+1 for creating forks of well-known projects those we may want to use as
module under mesos github. And for the rest of the lesser known
projects, we may create a github project under mesos that will only list
down those projects.
On Thursday 12 May 2016 02:16 PM, Jay JN Guo wrote:
Hi folks,
As we are all excited of Mesos modulerization that custom components can be
easily plugged in, I want to initiate this discussion on how we host and
maintain those module projects.
A well-designed module may benefit a broad range of users and we see
modules as part of the Mesos ecosystem. Having a centralized catalog would
make it easier to browse and manage.
For example, we see many Mesos-related projects under
https://github.com/mesos , which could be an ideal place.
https://github.com/mesos/modules stands as an example/template that enables
people to quickly develop their own module.
We also need to decide on the couple of other things such as acceptance
criteria, maintenance, autonomy, etc. Essentially, we want to set
guidelines that developers can easily follow and contribute to the Mesos
ecosystem.
Your thoughts and comments are highly appreciated!
Cheers,
/Jay
