You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Rich Bowen <rb...@rcbowen.com> on 2020/07/17 18:44:50 UTC
Dev model questions (Was Re: ASF Slack for community?)
On 7/17/20 2:37 PM, Armstrong Foundjem wrote:
> Hello ASF community members:
> I am a research student on FOSS, and currently, I am looking into the Apache ecosystem to understand the release mechanisms that ASF projects follow/use. However, it’s not trivial to understand without the help of expects like you in the community.
>
> Please, can you help me out answer the following questions?
>
> 1. What is the release cycle of Apache projects (how many times a year does ASF releases a new version of it’s products)?
Each project makes its own decisions on this.
> 2. What release model / release process do projects follow? Are these models/process very strict or are they flexible for different projects to do things they own way?
Each project makes its own decisions on this.
> 3. Are ASF projects inter-dependent to each other during development cycle of each project is completely unique in following it’s own road map?
Each project makes its own decisions on this. There are some projects
that are interdependent, but it's not widespread.
>
> Thank you for your time in answering these questions.
>
> Best regards,
> Armstrong Foundjem,
> Ecole Polytechnique, Montreal, Canada
>
>> On Jul 17, 2020, at 10:48, Austin Bennett <wh...@gmail.com> wrote:
>>
>> Thanks, Julian,
>>
>> Ultimately, my question comes down to: is it OK to point people interested
>> in events for specific (in this case Beam) events to the communication
>> platform used by the wider asf community. I figure it is ideal to expand
>> the overall Apache tent/community. Though there are certainly tradeoffs.
>>
>> Unless needed, the question of which platform for the foundation to use
>> seems a separate discussion.
>>
>> Cheers,
>> Austin
>>
>>
>>
>>
>> On Thu, Jul 16, 2020 at 9:03 AM Julian Foad <ju...@apache.org> wrote:
>>
>>> On behalf of FOSS fans everywhere: please seriously consider using
>>> [Matrix], the Open federated standard system. It's perfect for this
>>> sort of community, with bridges to Slack and IRC and many other systems.
>>> In the last two years Matrix has leapt ahead of other contenders like
>>> XMPP and is becoming the Open system of choice adopted by organisations
>>> from Mozilla to universities and governments.
>>>
>>> It's a great platform for integrating the chat side, and even the
>>> presentation side through Jitsi, of online events. The matrix devs do
>>> it and wrote a blog post describing how:
>>> https://matrix.org/docs/guides/running-online-events
>>>
>>> Before any of us risks pushing another FOSS community into the
>>> proprietary silo trap, let's pause and consider how we all would in fact
>>> be paying for it if it's "free as in beer". I've been watching this
>>> space since five years ago when the FOSS alternatives were weak, and now
>>> I'm really excited to see that, with the overwhelming global need for
>>> such a thing, Matrix has grown strong and is accelerating rapidly.
>>>
>>> I would strongly encourage the ASF membership to deploy their own Matrix
>>> server ASAP as it's the perfect fit for this sort of organization. I
>>> run a personal Matrix server and benefit from modern multi-device
>>> single-app access to all my IRC messaging (via a public bridge), all my
>>> WhatsApp messaging (via a private bridge), some private notes like
>>> diaries, as well as federated native Matrix messaging.
>>>
>>> I can give more detailed advice and put you in touch with specific
>>> contacts.
>>>
>>> - Julian
>>>
>>>
>>> See:
>>>
>>> * https://matrix.org -- for an introduction to Matrix
>>>
>>> * https://matrix.org/docs/guides/running-online-events -- see above
>>>
>>> * https://element.io/blog/welcome-to-element/ -- for an introduction to
>>> the top company/brand of Matrix services and apps (a bit like how Redhat
>>> is to Linux)
>>>
>>> * https://sifted.eu/articles/element-germany-deal/ -- news about big
>>> government deployments of Matrix
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>>
>
>
--
Rich Bowen - rbowen@rcbowen.com
@rbowen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org
Re: Dev model questions (Was Re: ASF Slack for community?)
Posted by Patricia Shanahan <pa...@acm.org>.
On 7/17/2020 11:44 AM, Rich Bowen wrote:
>
>
> On 7/17/20 2:37 PM, Armstrong Foundjem wrote:
>> Hello ASF community members:
>> I am a research student on FOSS, and currently, I am looking into the
>> Apache ecosystem to understand the release mechanisms that ASF
>> projects follow/use. However, it’s not trivial to understand without
>> the help of expects like you in the community.
>>
>> Please, can you help me out answer the following questions?
>>
>> 1. What is the release cycle of Apache projects (how many times a year
>> does ASF releases a new version of it’s products)?
>
> Each project makes its own decisions on this.
To expand a little on this, each project has a Project Management
Committee. The decisions you are asking about are made for each project
by its PMC.
The central organization is mainly concerned with providing some
infrastructure, a non-profit framework, and ensuring each project has a
healthy community with a functioning PMC to make its decisions.
If you want to understand ASF better, I suggest picking a few projects
that interest you and, for each PROJECT_NAME, subscribing to
dev@PROJECT_NAME.apache.org. There you will see the project in action.
>
>> 2. What release model / release process do projects follow? Are these
>> models/process very strict or are they flexible for different projects
>> to do things they own way?
>
> Each project makes its own decisions on this.
>
>> 3. Are ASF projects inter-dependent to each other during development
>> cycle of each project is completely unique in following it’s own road
>> map?
>
> Each project makes its own decisions on this. There are some projects
> that are interdependent, but it's not widespread.
>
>>
>> Thank you for your time in answering these questions.
>>
>> Best regards,
>> Armstrong Foundjem,
>> Ecole Polytechnique, Montreal, Canada
>>
>>> On Jul 17, 2020, at 10:48, Austin Bennett
>>> <wh...@gmail.com> wrote:
>>>
>>> Thanks, Julian,
>>>
>>> Ultimately, my question comes down to: is it OK to point people
>>> interested
>>> in events for specific (in this case Beam) events to the communication
>>> platform used by the wider asf community. I figure it is ideal to
>>> expand
>>> the overall Apache tent/community. Though there are certainly
>>> tradeoffs.
>>>
>>> Unless needed, the question of which platform for the foundation to use
>>> seems a separate discussion.
>>>
>>> Cheers,
>>> Austin
>>>
>>>
>>>
>>>
>>> On Thu, Jul 16, 2020 at 9:03 AM Julian Foad <ju...@apache.org>
>>> wrote:
>>>
>>>> On behalf of FOSS fans everywhere: please seriously consider using
>>>> [Matrix], the Open federated standard system. It's perfect for this
>>>> sort of community, with bridges to Slack and IRC and many other
>>>> systems.
>>>> In the last two years Matrix has leapt ahead of other contenders like
>>>> XMPP and is becoming the Open system of choice adopted by organisations
>>>> from Mozilla to universities and governments.
>>>>
>>>> It's a great platform for integrating the chat side, and even the
>>>> presentation side through Jitsi, of online events. The matrix devs do
>>>> it and wrote a blog post describing how:
>>>> https://matrix.org/docs/guides/running-online-events
>>>>
>>>> Before any of us risks pushing another FOSS community into the
>>>> proprietary silo trap, let's pause and consider how we all would in
>>>> fact
>>>> be paying for it if it's "free as in beer". I've been watching this
>>>> space since five years ago when the FOSS alternatives were weak, and
>>>> now
>>>> I'm really excited to see that, with the overwhelming global need for
>>>> such a thing, Matrix has grown strong and is accelerating rapidly.
>>>>
>>>> I would strongly encourage the ASF membership to deploy their own
>>>> Matrix
>>>> server ASAP as it's the perfect fit for this sort of organization. I
>>>> run a personal Matrix server and benefit from modern multi-device
>>>> single-app access to all my IRC messaging (via a public bridge), all my
>>>> WhatsApp messaging (via a private bridge), some private notes like
>>>> diaries, as well as federated native Matrix messaging.
>>>>
>>>> I can give more detailed advice and put you in touch with specific
>>>> contacts.
>>>>
>>>> - Julian
>>>>
>>>>
>>>> See:
>>>>
>>>> * https://matrix.org -- for an introduction to Matrix
>>>>
>>>> * https://matrix.org/docs/guides/running-online-events -- see above
>>>>
>>>> * https://element.io/blog/welcome-to-element/ -- for an introduction to
>>>> the top company/brand of Matrix services and apps (a bit like how
>>>> Redhat
>>>> is to Linux)
>>>>
>>>> * https://sifted.eu/articles/element-germany-deal/ -- news about big
>>>> government deployments of Matrix
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>>
>>
>>
>
--
This email has been checked for viruses by AVG.
https://www.avg.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org