incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <>
Subject Re: [DISCUSS] move the Incubator Report section to SVN or GIT?
Date Mon, 08 Aug 2016 19:35:54 GMT
On Mon, Aug 8, 2016 at 11:28 AM, John D. Ament <> wrote:
> How hard would that be?

To be brutally honest: to me (as the original author of the code),
fairly easy.  For others, perhaps not so much.

I would be quite willing to do the bulk of the initial work enabling
this.  It would be my hope that there would be at least one person who
was capable of running this code on their own machine (prereqs: at
least one of the following: a machine running Linux, Mac OS/X, Docker
or VirtualBox/Vagrant), and interested in making tweaks after the
basics are in place.

> is there data we could seed?

Actually, yes.  Every month we have a board report from the Incubator,
in text format, in SVN.

The way the board agenda tool works is that it parses this data into
JSON which is then used by the client.  ASF Officers and Members can
an example of the results here:

So the first step would be to parse the data into individual reports.
I've already got the basics for that in the board minutes tool.  Code:
; output: .  This could be
presented as individual pages in the board agenda tool.

Next step would be for draft minutes to be available someplace (my
preference would be svn).  It would need to be someplace with a large
set of people who have access than just officers and members.  That
data could be parsed by the same code and be presented as separate

None of the above is hard.  The hardest part will be tweaking the
authentication to allow only a subset of people to see the full
agenda, and a wider set of people to see the incubator parts.

What would be next is deciding what buttons and actions should be
supported.  This is truly the fun part.  Adding a button for moderator
approval is a matter of a few lines, as is the back end code that
makes the change to the text file and commits the result.  If there
are people who are interested, I can point to examples of how to do
this; otherwise I can make these changes.

All of this can be developed and tested on your own machine, and will
automatically be deployed via a push.

Instructions on getting started (including running tests) can be found here:

- Sam Ruby

> On Mon, Aug 8, 2016 at 9:04 AM Sam Ruby <> wrote:
>> On Mon, Aug 8, 2016 at 4:06 AM, Daniel Gruno <> wrote:
>> > On 08/08/2016 10:03 AM, Christopher wrote:
>> >> On Mon, Aug 8, 2016 at 3:34 AM Mark Struberg <
>> >
>> >> wrote:
>> >>
>> >>> Another possible option would be to move it to our CMS.
>> >>>
>> >>> That would bring us SVN for the people who prefer vi, but also a
>> graphical
>> >>> UI for editing.
>> >>> And it would make people make familiar with our CMS.
>> >>
>> >>
>> >> I prefer the Wiki over CMS. I find CMS to be clumsy and annoying. I'm
>> glad
>> >> the projects I'm involved in no longer use (or never have used) it. I'd
>> be
>> >> willing to use SVN (reluctantly, and with git-svn), but if it were tied
>> to
>> >> CMS, there'd still be the second publication step using CMS which would
>> be
>> >> annoying.
>> >>
>> >> There is something to be said about the low barrier to entry of a Wiki,
>> >> though. Anybody can do it. It's the least developer-centric way of doing
>> >> things out there. I know CMS tries to be that, but it hasn't quite
>> >> succeeded.
>> >
>> > Why not make a whimsy-like application for this? That would ensure that
>> > you are only meddling with the specific sub-section of the report you
>> > are working on, and would allow multiple people to work on the report at
>> > the same time, maybe even have a simple sign-off button for mentors?
>> Or even adapt the current board agenda application to take a different
>> data source?
>> You could have svn as a data source, and have a web interface.
>> > Shouldn't take long to make that :)
>> >
>> > With regards,
>> > Daniel.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> > For additional commands, e-mail:
>> - Sam Ruby
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message