Re: [Cs-studio-core] Project organization

[Hatje, J. <jan...@de...>]

Hi,
 
we are still discussing the core organization and structure. We will
send an answer with our
opinion by the end of the week.
 
Best regards,
Jan 

	-----Original Message-----
	From: Carcassi, Gabriele [mailto:car...@bn...] 
	Sent: Wednesday, October 20, 2010 4:19 PM
	To: CSS-Core
	Subject: [Cs-studio-core] Project organization
	
	

	Hi,

	 

	I am following up from a discussion that Mathias started here at
BNL during the last Epics meeting. I am going to briefly report it here,
so that we can bring everybody in synch.

	 

	* Patches to plugins

	 

	First, is to establish a "procedure" on how to accept
contribution, so that it is clear for an external contributor how to
provide patches for a particular plugin. After discussion, we agreed
that the procedure should be "contact the plugin maintainer", who then
can decide how to coordinate depending on the size of the patch, the
status of that plugin development and the "trust" he has on the
contributor. I can prepare a wiki page with these options, mainly for
the inexperienced maintainer.

	 

	So the question becomes: how does someone know who is
maintaining a plugin? We agreed to use the actual definition in the
plugin overview itself (which goes in the manifest and is also available
at runtime). There is a better chance that this is well maintained, and
we can also later build a script to generate a web page from this.

	 

	Looking at the overview right now, there is a mixture of names
and/or site. I would propose the following format:

	Name Surname <email>[, Name Surname <email>] - Site

	For example:

	Gabriele Carcassi <car...@bn...>, Kunal Shroff
<ks...@bn...> - Brookhaven National Lab

	which means I am the primary maintainer, and Kunal is the
backup. Backup is optional. The site I am putting just because many
plugins currently have it. What do people think?

	 

	Once we settle, I will update the wiki with the information

	 

	* Technical lead group (don't remember exactly what was the
name)

	 

	Mathias proposed to form a lightweight group of technical people
who resolves technical organization issues. Such as: what goes into
core? How do we use branches in hg? How do we coordinate releases of
core plugins? How do we manage core dependencies? And so on. This would
be composed of actual core plugin maintainers plus a representative from
each site that is doing actual development on top of them.

	 

	* User vs Developer

	 

	There is still a certain amount of confusion on whether people
need Eclipse or not... I have put together something to clarify in the
form of a Quiz:

	https://sourceforge.net/apps/trac/cs-studio/wiki

	Let me know what you think... :-)

	 

	I hope I didn't forget anything...

	 

	Gabriele