Kepler Project (renewed) outline is online

[marbux]

Hi, all,

In my befuddled normal state, I tend toward storing my thoughts in a
written outline rather than in my head. I've begun going through the
various threads on this project in an attempt to outline areas of
consensus achieved and my own thoughts, clipping significant portions
of emails.

I still have a lot of threads to go through, but others may find the
outline useful. It's online at
<https://sites.google.com/site/marbux/home/kepler-project-renewed>.
I'll update it as I go along.

Best regards,

Paul

[Thijs Schreijer]

Excellent!

> --
> You received this message because you are subscribed to the Google Groups
> "luaforwindows" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to luaforwindow...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

[Thijs Schreijer]

Paul,

 

I don't know how you set this up (markdown or html, or generated otherwise), but would it be possible to put the source text in a github repo? That would allow us to help update element/ideas as pull requests. These can be easily discussed on github and when agreed integrated.

 

comment;

text says: "Modules included will all be MAINTAINED", I think it should also state WHO will maintain, would that be the project taking on maintenance of all included modules, or is it meant that only maintained modules will be included?

 

Thijs

[marbux]

On Sat, Mar 30, 2013 at 12:02 PM, Thijs Schreijer
<th...@thijsschreijer.nl> wrote:

> I don't know how you set this up (markdown or html, or generated otherwise),

It's otherwise, generated by export to what is essentially HTML 3.2 of
a NoteCase Pro outline with automatic generation of a linked table of
contents.

> but would it be possible to put the source text in a github repo? That would
> allow us to help update element/ideas as pull requests. These can be easily
> discussed on github and when agreed integrated.

Good idea. I may need to do a bit of reformatting, depending on what
github wants. I'll aim to get that done sometime today.

> comment;
> text says: "Modules included will all be MAINTAINED", I think it should also
> state WHO will maintain, would that be the project taking on maintenance of
> all included modules, or is it meant that only maintained modules will be
> included?

That needs discussion. As I recall, Peter S. originally suggested this
with "maintained" in all caps and you incorporated that into to your
list. I don't recall any discussion of who would do the maintaining.

For those who want to see the context of "MAINTAINED," it's at
<https://sites.google.com/site/marbux/home/kepler-project-renewed#BUDlgVwbXEoGXRw3BxCcpg>,
the section with draft notes on the distribution project deliverable
consensus points.

Best regards,

Paul

[marbux]

Thjis, the source is up now at <https://github.com/Marbux/Kepler-Dist-Notes>.

I've removed node numbering because these will change as nodes are
added and removed, which makes them poor reference points for a living
document. But it's a moment's work to restore numbering if you'd
prefer that.

What do you think of the idea of mirroring the content in rendered
form as the repo Readme? I'd need to find an html2md converter that
outputs git's flavor of markdown. But I presume that wouldn't be hard
to find.

Best regards,

Paul

[Andrew Starks]

Hey Paul, have you checked out Trello.com for this? It's a free site for project management and it works great for stuff like this. It's worth a peek at least. 

-Andrew 

[marbux]

On Sat, Mar 30, 2013 at 6:57 PM, Andrew Starks <andrew...@trms.com> wrote:

> Hey Paul, have you checked out Trello.com for this? It's a free site for
> project management and it works great for stuff like this. It's worth a peek
> at least.

I peeked, actually a bit more than that. First impression is that it
looks very useful for managing a multiple participant project but
would take more commitment to the role of a project administrator than
I want to take on.

I've got enough project management experience to recognize that I'm
not the right guy to play the project admin role in this one.

Best regards,

Paul

[Andrew Starks]

On Saturday, March 30, 2013, marbux wrote:

That's cool. We just use it by dumping each topic onto a card. Then comments, checklists pictures, etc, sort of... Take over. 

It's all very collaborative, but it very well may be completely different than what you are up to. Some of the nouns and verbs that you were using reminded me of it.

Glad you were able to check it out, though.  

[marbux]

On Sat, Mar 30, 2013 at 9:24 PM, Andrew Starks <andrew...@trms.com> wrote:
>

> It's all very collaborative, but it very well may be completely different
> than what you are up to. Some of the nouns and verbs that you were using
> reminded me of it.

That conceivably might be because I've spent a fair bit of time
looking over IT standards as part of my study of international law
governing software interoperability. I borrowed some IT standard
technical committee charter concepts for organizing the outline.

Best regards,

Paul

[Thijs Schreijer]

> -----Original Message-----
> From: luafor...@googlegroups.com
> [mailto:luafor...@googlegroups.com] On Behalf Of marbux

How about the other way around; source as the readme.md and output rendered html. Makes it easy to edit right on the github site, and always displays properly on github as well. When posting elsewehere, put it through an html generator.

[marbux]

On Sat, Mar 30, 2013 at 11:43 PM, Thijs Schreijer
<th...@thijsschreijer.nl> wrote:

> How about the other way around; source as the readme.md and output rendered html. Makes it easy to edit right on the github site, and always displays properly on github as well. When posting elsewehere, put it through an html generator.

Does this work for you? <https://github.com/Marbux/Kepler-Dist-Notes#readme>.

Best regards,

Paul