>but we can make this manageable by > progressing step by step. Agree. I honestly don't have time to keep up with gitter, but if the list of tasks is clearly broken down into small steps and articulated on dev@, it seems like it would be easier for more people to participate.
Keeping code that needs a lot of work in a separate location makes a lot of sense to me. Gale On Sun, Mar 12, 2017, 1:46 AM Andy Seaborne <a...@apache.org> wrote: > > > On 01/03/17 15:06, Stian Soiland-Reyes wrote: > > On Wed, 1 Mar 2017 08:44:27 +0000, Andy Seaborne <a...@apache.org> > wrote: > >> Ian's put some notes in but it needs completing. > >> > >> Where is everyone? > >> > >> There has been a big dropoff of activity on dev@ in this reporting > period. > > > > Thanks. I augmented the report a bit: > > > >> How has the community developed since the last report? > >> > >> List has gone a bit more quiet, while activity on the > >> Gitter chat https://gitter.im/apache/taverna > >> has remained at same level. Need to re-focus use of > >> mailing list and community development. > > > >> > >> Comments: > >> Activity has stalled a bit in the drive towards graduation, as > >> some (perhaps tedious) IP review remains. Ambition levels > >> might need adjustment, e.g. don't include all repositories > >> in graduation to TLP. > > > > Agree there has been a big dropoff in the dev@ activity - not sure how > much we > > can blame this on the Gitter chat (which has not been as quiet), but we > should > > refocus our activity here on this list. > > Gitter is great for within team discussions but it's pretty opaque to > people outside, which is the value of dev@ > > > I know I am partially to blame as I have not been able to contribute > much these > > months - it's been quite hectic with work; lots of documents, emails and > calls, > > and I have not been able to help where I should. > > > > I must admit I have lacked motiviation to help on the remaining IP > review - > > it's not something that is too easy to pick up late at night when the > kids > > are at bed.. I might not be alone here - but we can make this manageable > by > > progressing step by step. > > > > > > Andy - do you think if we don't include a repository in graduation it > would be > > easy to add back on later from GitHub? As it's not SVN it is not as easy > to > > keep around; I know this helped in Jena, where you had some "extra > stuff" at an > > SVN tag that you could pick up again at a later time. Perhaps we could > do some > > kind of "legacy" or "sandbox" apache-taverna git repository with specific > > branches under there? > > At graduation, what is in Apache source code control will need to be > IP-clean. Incubation has more latitude. > > There is no distinction of some repos of a TLP being "good" and some > "parking space" that I know of. People are free to pick up Apache code > direct from repos and some notes in a README don't really meet a > reasonable level of notice. > > You can keep code elsewhere and contribute later. > > Andy > > > > > >
