Citerias to become a Ceph project

Citerias to become a Ceph project

[Loic Dachary]

[-- Attachment #1: Type: text/plain, Size: 2266 bytes --]

Hi Ceph,

The title sounds a little strange (Citerias to become a Ceph project) because I'm not aware of projects initiated by someone external to Ceph that later became part of the Ceph nebula of projects (as found at http://tracker.ceph.com/projects/ or http://github.com/ceph/). I can however imagine that a piece of software developed with no interaction with the Ceph development community could be contributed and become a valuable addition (port to non GNU/Linux Operating Systems, monitoring applications for mobile devices etc.).

Although publishing the code of such a component under a Free Software license is a natural first step, there is more to do before it becomes part of what we (the community of Ceph developers) care for on a regular basis. Borrowing the OpenStack requirements ( at http://governance.openstack.org/reference/new-projects-requirements.html ), it could be expressed as:

    Free Software:
        The proposed project uses a Free Software license as published at http://www.gnu.org/licenses/license-list.html#SoftwareLicenses
        Project must have no library dependencies which effectively restrict how the project may be distributed or deployed
    Open Community:
        The leadership is chosen by the contributors to the project
        The project has regular public meetings on IRC and those meetings are logged and published
    Open Development:
        The project uses public code reviews 
        The project has core reviewers and adopts a test-driven gate
        The project provides liaisons that serve as contacts for the work of cross-project teams in Ceph
        Where it makes sense, the project cooperates with existing projects rather than gratuitously competing or reinventing the wheel
        Where appropriate, the project adopts technology and patterns used by existing Ceph projects
    Open Design:
        The project direction is discussed at the Ceph Design Summit and/or on public forums
        The project uses the ceph-devel ML to discuss issues

These requirements are formal in the case of OpenStack but they could also be used in the context of Ceph, not as requirements but as a guideline.

What do you think ?

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Requirements to become a Ceph project

[Loic Dachary]

[-- Attachment #1: Type: text/plain, Size: 2457 bytes --]

The title sound even stranger with non-english words in it. Please excuse the frenchism :-)

On 28/07/2015 08:38, Loic Dachary wrote:
> Hi Ceph,
> 
> The title sounds a little strange (Citerias to become a Ceph project) because I'm not aware of projects initiated by someone external to Ceph that later became part of the Ceph nebula of projects (as found at http://tracker.ceph.com/projects/ or http://github.com/ceph/). I can however imagine that a piece of software developed with no interaction with the Ceph development community could be contributed and become a valuable addition (port to non GNU/Linux Operating Systems, monitoring applications for mobile devices etc.).
> 
> Although publishing the code of such a component under a Free Software license is a natural first step, there is more to do before it becomes part of what we (the community of Ceph developers) care for on a regular basis. Borrowing the OpenStack requirements ( at http://governance.openstack.org/reference/new-projects-requirements.html ), it could be expressed as:
> 
>     Free Software:
>         The proposed project uses a Free Software license as published at http://www.gnu.org/licenses/license-list.html#SoftwareLicenses
>         Project must have no library dependencies which effectively restrict how the project may be distributed or deployed
>     Open Community:
>         The leadership is chosen by the contributors to the project
>         The project has regular public meetings on IRC and those meetings are logged and published
>     Open Development:
>         The project uses public code reviews 
>         The project has core reviewers and adopts a test-driven gate
>         The project provides liaisons that serve as contacts for the work of cross-project teams in Ceph
>         Where it makes sense, the project cooperates with existing projects rather than gratuitously competing or reinventing the wheel
>         Where appropriate, the project adopts technology and patterns used by existing Ceph projects
>     Open Design:
>         The project direction is discussed at the Ceph Design Summit and/or on public forums
>         The project uses the ceph-devel ML to discuss issues
> 
> These requirements are formal in the case of OpenStack but they could also be used in the context of Ceph, not as requirements but as a guideline.
> 
> What do you think ?
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Requirements to become a Ceph project

[Joao Eduardo Luis]

On 07/28/2015 07:59 AM, Loic Dachary wrote:
> The title sound even stranger with non-english words in it. Please excuse the frenchism :-)

I think 'criteria' is fine in this context, and more to the point that
'requirements'.  Then again, I'm not a native speaker ;)

  -Joao

> 
> On 28/07/2015 08:38, Loic Dachary wrote:
>> Hi Ceph,
>>
>> The title sounds a little strange (Citerias to become a Ceph project) because I'm not aware of projects initiated by someone external to Ceph that later became part of the Ceph nebula of projects (as found at http://tracker.ceph.com/projects/ or http://github.com/ceph/). I can however imagine that a piece of software developed with no interaction with the Ceph development community could be contributed and become a valuable addition (port to non GNU/Linux Operating Systems, monitoring applications for mobile devices etc.).
>>
>> Although publishing the code of such a component under a Free Software license is a natural first step, there is more to do before it becomes part of what we (the community of Ceph developers) care for on a regular basis. Borrowing the OpenStack requirements ( at http://governance.openstack.org/reference/new-projects-requirements.html ), it could be expressed as:
>>
>>     Free Software:
>>         The proposed project uses a Free Software license as published at http://www.gnu.org/licenses/license-list.html#SoftwareLicenses
>>         Project must have no library dependencies which effectively restrict how the project may be distributed or deployed
>>     Open Community:
>>         The leadership is chosen by the contributors to the project
>>         The project has regular public meetings on IRC and those meetings are logged and published
>>     Open Development:
>>         The project uses public code reviews 
>>         The project has core reviewers and adopts a test-driven gate
>>         The project provides liaisons that serve as contacts for the work of cross-project teams in Ceph
>>         Where it makes sense, the project cooperates with existing projects rather than gratuitously competing or reinventing the wheel
>>         Where appropriate, the project adopts technology and patterns used by existing Ceph projects
>>     Open Design:
>>         The project direction is discussed at the Ceph Design Summit and/or on public forums
>>         The project uses the ceph-devel ML to discuss issues
>>
>> These requirements are formal in the case of OpenStack but they could also be used in the context of Ceph, not as requirements but as a guideline.
>>
>> What do you think ?
>>
> 

Re: Requirements to become a Ceph project

[Mark Nelson]

My first reading of the topic was "Citerias (ie a project named 
Citerias) to become a Ceph project".  It wasn't until I re-read it more 
closely that I realized it was criteria.  :)

On 07/28/2015 12:51 PM, Joao Eduardo Luis wrote:
> On 07/28/2015 07:59 AM, Loic Dachary wrote:
>> The title sound even stranger with non-english words in it. Please excuse the frenchism :-)
>
> I think 'criteria' is fine in this context, and more to the point that
> 'requirements'.  Then again, I'm not a native speaker ;)
>
>    -Joao
>
>>
>> On 28/07/2015 08:38, Loic Dachary wrote:
>>> Hi Ceph,
>>>
>>> The title sounds a little strange (Citerias to become a Ceph project) because I'm not aware of projects initiated by someone external to Ceph that later became part of the Ceph nebula of projects (as found at http://tracker.ceph.com/projects/ or http://github.com/ceph/). I can however imagine that a piece of software developed with no interaction with the Ceph development community could be contributed and become a valuable addition (port to non GNU/Linux Operating Systems, monitoring applications for mobile devices etc.).
>>>
>>> Although publishing the code of such a component under a Free Software license is a natural first step, there is more to do before it becomes part of what we (the community of Ceph developers) care for on a regular basis. Borrowing the OpenStack requirements ( at http://governance.openstack.org/reference/new-projects-requirements.html ), it could be expressed as:
>>>
>>>      Free Software:
>>>          The proposed project uses a Free Software license as published at http://www.gnu.org/licenses/license-list.html#SoftwareLicenses
>>>          Project must have no library dependencies which effectively restrict how the project may be distributed or deployed
>>>      Open Community:
>>>          The leadership is chosen by the contributors to the project
>>>          The project has regular public meetings on IRC and those meetings are logged and published
>>>      Open Development:
>>>          The project uses public code reviews
>>>          The project has core reviewers and adopts a test-driven gate
>>>          The project provides liaisons that serve as contacts for the work of cross-project teams in Ceph
>>>          Where it makes sense, the project cooperates with existing projects rather than gratuitously competing or reinventing the wheel
>>>          Where appropriate, the project adopts technology and patterns used by existing Ceph projects
>>>      Open Design:
>>>          The project direction is discussed at the Ceph Design Summit and/or on public forums
>>>          The project uses the ceph-devel ML to discuss issues
>>>
>>> These requirements are formal in the case of OpenStack but they could also be used in the context of Ceph, not as requirements but as a guideline.
>>>
>>> What do you think ?
>>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>