Date: Fri, 29 Mar 2024 04:50:17 -0500 (CDT) Message-ID: <36683275.336.1711705817056@os-confluence.ncsa.illinois.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_335_286648311.1711705817056" ------=_Part_335_286648311.1711705817056 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
W= hich source control solution and development workflow will be used by the p= roject? Some options are:
Bitbucket - External Resource w=
here you can host closed-source projects. It can be linked to NCSA JIRA.
OpenS= ource Bitbucket - through Atlassian Opensource suite. The pro= jects that use this option needs to be open source
= GitHub - Very public, pretty close to the de-facto standard for ho= sting open source projects
=
GitLab - Can use the external/p=
ublic one, or the NCSA hosted one (https://git.ncsa.illinois.edu/). The NCSA hosted one can be used for =
closed-source projects, a drawback is that it cannot be connected to JIRA r=
ight now.
My recommendations in general are:
- github.com if yo=
ur project is opensource and you want external collaborators and make it ea=
sy to find
- git.ncsa.illinois.edu=
a> if your project is private and you don't want to host the =
code external, you can add people using the NCSA identity system
- bitbucket.com =
;if your project is private but you want external people and want to host i=
t outside of NCSA
- opensource.ncsa.=
illinois.edu if your project is public but don't want to =
host it on github (for example you like jira/confluence/etc)
What we d= o is host our projects on opensource and then push the master branch to git= hub, to get the public feel, but have more control over the branches and ji= ra tickets.