Skip to content

Just did some minor UI changes in community.html #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Just did some minor UI changes in community.html #26

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions community.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,25 +90,25 @@
<a
href="http://bit.ly/camicroscope"
>
<button class="section__button__colored">Join our Slack</button>
<button class="section__button__colored mb-5">Join our Slack</button>
</a>
</div>
<p class="section__content__main">
<p class="section__content__main text-left my-3">
caMicroscope is open source software. Much of its development has been ad-hoc towards particular project needs. Thanks to community support, caMicroscope is able to be a general tool, in addition to these specific use cases.
</p>
<p class="section__content__main">
<p class="section__content__main text-left my-3">
The clearest and most structured way in which the community supports caMicroscope's and its scientific missions is through <a href="https://summerofcode.withgoogle.com/">Google Summer of Code (GSOC)</a>. This program allows for contributors to recieve a stipend and formal acknowledgment for open source contributions.
</p>
<p class="section__content__main">
<p class="section__content__main text-left my-3">
caMicroscope can be a difficult project to onboard onto. Since it is a distributed platform, development of the components occurs in different repositories. The best starting place is the <a href="https://github.com/camicroscope/distro">distribution repository</a>, which has a docker-compose container manifest for comparatively easy deployment of the platform all at once. For development purposes, we have a special manifest, develop.yml, which disables some security features, and uses edge code. From there, use the UI, which detaults to port 4010) to load an image.
</p>
<p class="section__content__main">
<p class="section__content__main text-left my-3">
We Use <a href="https://guides.github.com/introduction/flow/index.html">Github Flow</a>, So All Code Changes Happen Through Pull Requests. Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests. We do not typically assign pull requests without a reason why a particular person should do the work.
</p>
<p class="section__content__main">
<p class="section__content__main text-left my-3">
As a general a open source quality of life improvement, we recommend working on topic branches off of your fork, and keeping your master/develop up to date with the upstream repositories. There's <a href="https://gist.github.com/anjohnson/8994c95ab2a06f7d2339">a guide to triangle workflows</a> which may be helpful for using git this way.
</p>
<p class="section__content__main">
<p class="section__content__main text-left my-3">
Issues and pull requests should be against the most relevant repository (i.e. where the change would take place).
<b>Great Bug Reports</b> tend to have:<br/>
A quick summary and/or background<br/>
Expand Down