Create repository hosting guidelines

Arturas-K commented 7 years ago

We need to have a set of guidelines for repositories that we going to host under Callcredit organisations. Guidelines should cover these questions:

what repos are good candidates?
what repos are not allowed?
how maintainers should be organised?
what is our minimum commitment for maintaining hosted repos?
what should be included in each repo (readme.md, code of conduct, licence etc)?

Arturas-K commented 7 years ago

@ColinM9991 @Edgixshua @sqldan please have a look

ColinM9991-zz commented 7 years ago

I'm also interested in this and it may be good to have a group chat during the week.

We're currently working on a Problem+Json package for ASP.NET Core which provides an implementation for the Problem+Json standard in C# and is definitely a good candidate for open sourcing as it is not a company-specific implementation, but the question is what level of commitment will we have following the open sourcing of this. Particularly how we have separation between our current approach for work items and stories on our backlog with open-source repositories.

Edgixshua commented 7 years ago

I think we also need to take into account people's profiles. If you make your organisation information public then you need to bear in mind that for every contribution you make to any project, people can see that you are affiliated with Callcredit (I have mine set to private so people can't see what organisations I'm a member of - this is the default setting).

Arturas-K commented 7 years ago

This is covered by code of conduct scope part. When you are part of Callcredit organisation you must comply with code of conduct. Also i want to have Organisation visible on people's profiles as this will promote Callcredit name.

Arturas

From: Joshua Sheffield notifications@github.com Sent: Tuesday, August 22, 2017 10:50:53 AM To: CallCreditGroup/Policies Cc: Arturas Kuznecovas; Author Subject: Re: [CallCreditGroup/Policies] Create repository hosting guidelines (#2)

I think we also need to take into account people's profiles. If you make your organisation information public then you need to bear in mind that for every contribution you make to any project, people can see that you are affiliated with Callcredit (I have mine set to private so people can't see what organisations I'm a member).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/CallCreditGroup/Policies/issues/2#issuecomment-323947644, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APcP7SRSx3araKhZn5bge5p1NJclh79pks5saohcgaJpZM4O90h6.

DannyArr commented 7 years ago

Agreed. And if you don't want to link CallCredit to your own profile, you can create a new profile to provide that separation.

How do we define what we consider to be intellectual property, and what we want to share. What about licencing? https://opensource.org/licenses

DannyArr commented 7 years ago

Ah, just saw the licencing issue :D

Arturas-K commented 7 years ago

will have to hold this one. Same as #3, we are not going to allow hosting repos for now.

Callcredit / Policies

Create repository hosting guidelines #2