fluid-lab GitHub organization

[Tony Atkins]

Hi, Justin:

Now that I'm actually considering submitting something to fluid labs, I
have a practical question about the process here.  For GPII contrib
projects, we request a new repo, and then fork/branch and submit our
contribution as a pull request against the new repo.  This allows us to
have an initial pull request review for the project, which is a good
opportunity to discuss best practices and review the quality together.

I know we're in a transitional state here, so I understand moving in
existing projects via ownership transfers.  What about new projects?
Should they follow the same process as we use with GPII contributions?
What does everyone else think?

Cheers,


Tony

On Fri, Feb 3, 2017 at 3:05 PM, Justin Obara <obara.justin at gmail.com> wrote:

>
> I’ve created a new GitHub organization called “fluid-lab
> <https://github.com/fluid-lab>”. fluid-lab will be a separate GitHub
> organization as a place where the community can share, track and
> collaborate on our experimental and exploratory work. For a start, I’ve
> forked last years GSoC projects and the OER project from our recent co-op
> students into the space. I’ll be confirming with the owners of those repos
> if they’d like to transfer ownership to fluid-lab.
>
> If you have a project that you feel would be appropriate to be included in
> fluid-lab please let us know.
>
> For transfers, please see ( https://help.github.com/
> articles/about-repository-transfers/ ).
>
> Thanks
> Justin
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170209/043349e0/attachment.html>