[Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED

[Ildiko Vancsa]

Hi,

I got feedback from users as well on the desire of having the flock services available standalone. I know it is not a priority at this point, but in my understanding we all acknowledged that this is something we would like to achieve. It makes me wonder if merging the project teams will make it harder to start that process and reach that goal?

The current setup covers quite separate areas from functionality point of view which could make it harder for new contributors to find where to contribute once the teams are merged to cover all these areas.

In that sense I think we should give it some thought how to name the new team if that is the move where the community and affected team members are leaning towards. I think ‘platform' is misleading as StarlingX itself is an integrated platform which means that we could merge a couple more teams into this one like networking for instance that does not have a dedicated repository at this point. Looking at the list of project teams it also doesn’t look like a match to the flock services either. Any thoughts on this from others?

Once the teams and the community come to a decision we should make sure the wiki is updated accordingly and I also agree to setup weekly meetings to improve communication and visibility.

Thanks,
Ildikó


> On 2019. Oct 1., at 2:00, Saul Wold <sgw at linux.intel.com> wrote:
> 
> 
> 
> On 9/30/19 3:52 PM, Xie, Cindy wrote:
>> We have one customer in China evaluated these "Flocks" services, and they want to use them as building blocks into their product, but will do it one by one. Will the repo merge impact the possibility of customer of doing so?
> I think this needs to be clarified, I do not think that the repos are being merged, just the project team so that there will be one "Flock" meeting wit a common PL / TL pair.
> 
> 
> Sau!
> 
> 
>> Thx. - cindy
>> -----Original Message-----
>> From: Jones, Bruce E <bruce.e.jones at intel.com>
>> Sent: Tuesday, October 1, 2019 5:47 AM
>> To: Ildiko Vancsa <ildiko.vancsa at gmail.com>; starlingx <starlingx-discuss at lists.starlingx.io>
>> Subject: Re: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED
>> I have no objection to merging these projects.  I think it makes sense, for now.  Long term I think there is value in making the "Flock" projects more separate, and maybe even stand-alone, someday.
>> I think it would also be good for the teams working on these projects to hold public meetings and post agenda & minutes to the list.
>>       brucej
>> -----Original Message-----
>> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com]
>> Sent: Monday, September 30, 2019 5:38 AM
>> To: starlingx <starlingx-discuss at lists.starlingx.io>
>> Subject: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED
>> Hi,
>> I’m reaching out about an open review that proposes to merge six of the StarlingX projects into one: https://review.opendev.org/#/c/683410/
>> As this proposal affects 1/3 of the project teams I would like to have a community discussion about this rearrangement.
>> I have a few questions to discuss:
>> * Are all of these projects still active?
>> * From functionality perspective the project teams cover very different areas. What are the motivating factors behind the proposed change?
>> * Does this proposal help with organizing work and onboarding new contributors?
>> I would like to have feedback from the project team members and community members on the above questions as well as in general in response to the proposed change. Please respond to this thread and share your views.
>> I also checked some details and based on the StarlingX wiki the projects listed in the subject have no meetings and their wiki pages are also very brief in providing information about what they do and how to participate. I think this is something to look into in general and it should be the responsibility of all project teams and contributors.
>> I propose to have a liaison from every team to look into addressing this topic to make sure this is an ongoing activity along with the technical development work. What do you think about this idea?
>> Thanks and Best Regards,
>> Ildikó
>> _______________________________________________
>> Starlingx-discuss mailing list
>> Starlingx-discuss at lists.starlingx.io
>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>> _______________________________________________
>> Starlingx-discuss mailing list
>> Starlingx-discuss at lists.starlingx.io
>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>> _______________________________________________
>> Starlingx-discuss mailing list
>> Starlingx-discuss at lists.starlingx.io
>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss