[TCLCORE] Resend: Re: TIP process

It appears this didn’t make it to the list.
---------- Forwarded message ----------

From: Steve Landers <ste...@digitalsmarties.com>
Date: 21 Feb 2018, 4:27 PM +0800
To: Jan Nijtmans <jan....@gmail.com>, Harald Oehlmann <hara...@elmicron.de>, Zaumseil René <RZau...@kkg.ch>
Cc: Martin Lemburg <mart...@gmx.net>, Tcl Core List <tcl-...@lists.sourceforge.net>
Subject: Re: TIP process

> Thanks for your thoughts René.>> As discussed on the Tclers Chat, the process could indeed do with some refinement.>> TIP #2 outlines the existing workflow https://core.tcl-lang.org/tips/doc/trunk/tip/2.md.    In particular, it states that the TIP editor (Donal) is responsible for assigning numbers to each TIP and managing its status on behalf of authors.  Arguably that has become a bottleneck, and a burden for Donal.>> My suggestion (based on your input) would be to use the Core Tickets at https://core.tcl-lang.org/tips/ticket to propose a TIP.   Any of the TCT members could then “sponsor” the TIP by assigning a number, creating the entry in the TIP table at https://tip.tcl-lang.org and granting the proposer core developer rights on Fossil.  We should also configure the ticket system to issue automatic notifications to TCT members via TCLCORE,  to get as many eyes as we can.>> From then on I would suggest the TIP maintenance is done through the existing TIP system and submitting code through branches in Fossil (i.e. rather than attaching files to tickets).>> We should add comments at the top of the Ticket page, the Tip page and the Core home page pointing newcomers to TIP #2.>> If this proposal (or a variation) was to be accepted we’d need a process TIP to amend TIP #2 accordingly.   Kevin Kenny and myself can work on that.>> Let the bikeshedding begin :)>> Steve>> On 20 Feb 2018, 4:33 PM +0800, Zaumseil René <RZau...@kkg.ch>, wrote:> >> > Hi all,> >> > Here are my opinion as a long time user and sometime tip editor.> >> > 1. As a newcomer it is not clear where to start.> > Currently sending a mail to this list or asking on the chat is a starting point.> > Imho this should be at least mentioned on the home page of the tip's.> >> > 2. The next step after creation of the tip is the implementation.> > Without access to the core I have to find someone to include the changes.> > Again there is no place where I should send my changes.> >> > 3. If there is a implementation ready discussion starts.> > After the most pressing issues cleared there is often a gap. Nothing happened.> > May be setting here a time limit and after that time ask for a redelay or voting could help.> >> > 4. There is no summary of the current state of open tip's.> > When discussion restarts we have to search the archives first.> >> >> > IIRC there is a ticket system inside fossil. Would it be possible to use it with a workflow for tip's?> > Point 1. could then the creation of a new ticket. Moving to 2. is when the tct accept the idea.> > It could solve issue 2. with uploading the changed files as attachements.> >> >> > Regards> > René> > > __________ ______________________________> > > Von: Jan Nijtmans <jan....@gmail.com> > > Gesendet: Dienstag, 20. Februar 2018 08:55> > > An: Harald Oehlmann> > > Cc: Martin Lemburg; Tcl Core List> > > Betreff: Re: [TCLCORE] New TIP 501 - Add "string is dict" to string ensemble> > >> > > 2018-02-16 13:46 GMT+01:00 Harald Oehlmann:> > > > yes, the non-reaction of the TCT is indeed an issue keeping many wizards> > > > (like you) away from TCL. That is the nature of it, as they are all> > > > volonteers and can do what they like. The gems will just stay unlooked> > > > until they get old. It would be good to have a "vote force rule", so all> > > > projects get voted after a time delay, even if no sponsor is found.> > >> > > Well, let's react to that then ;-)> > >> > > Any TIP's people want votes on, simply can be requested on this mailing> > > list. Since TIP's are in fossil now, that process is much less restricted than> > > in the past: Anyone can write a TIP and request someone sponsoring it.> > > For Tcl 8.x, any TIP requesting a (potential) incompatibility will be received> > > with scepsis (e.g. TIP #448 and #476), but history shows that it's very> > > well possible. For Tcl 9 it will be easier to get such a TIP go though.> > >> > > So, I don't think a "vote force rule" will help: It only would receive more> > > NO votes than it would possibly get otherwise.> > >> > > Thanks!> > > Jan Nijtmans> >> >> > Kernkraftwerk Goesgen-Daeniken AG> > CH-4658 Daeniken, Switzerland> >> > Diese Nachricht (inkl. Anhaenge) beinhaltet moeglicherweise vertrauliche oder gesetzlich geschuetzte Daten oder Informationen. Zum Empfang derselben ist (sind) ausschliesslich die genannte(n) Person(en) bestimmt. Falls Sie diese Nachricht irrtuemlicherweise erreicht hat, sind Sie hoeflich gebeten, diese unter Ausschluss jeder Reproduktion zu vernichten und den Absender umgehend zu benachrichtigen. Besten Dank.> >> > ------------------------------------------------------------------------------> > Check out the vibrant tech community on one of the world's most> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot> > _______________________________________________> > Tcl-Core mailing list> > Tcl-...@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/tcl-core

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot