Bootstrapping the next generation of STeVe

[Daniel Gruno <hu...@apache.org>]

Hi folks,
As we have some renewed interest in working on STeVe, this would also be 
a good time to sort out some practicalities and names.

# Version control:
I think it would be a good move to switch to git for the next iteration. 
Not because I'm a fan of git in particular, but because of the added 
interactions with the larger community at GitHub, as well as the tools 
provided there.

If we do go down this road, the next step is to figure out how to have 
old steve and new steve side by side. We can either keep old steve on 
svn and make a new steve.git for the next gen product, or we can come up 
with some sort of (code)name for this next piece of software, such as 
steve-nextgen, steve-2, steve-buscemi etc. I don't have any good ideas 
myself just yet. Ideas are very much welcome here!

# Lingo etc:
I think we're pretty fixed on using Python 3 for this next version, 
which works out great for me personally as well as our newcomer Sean.
Front-end-wise we're probably looking at html+js with a json api or some 
such? Up for debate, do let me know what your thoughts are.

# Architecture:
TBD - I'll start some topics in separate threads on this.

Anywho, these are my thoughts/questions at the moment.

With regards,
Daniel.

Re: Bootstrapping the next generation of STeVe

[Rich Bowen <rb...@rcbowen.com>]

On Sat, Mar 5, 2022, 19:40 Sam Ruby <ru...@intertwingly.net> wrote:

> On Sat, Mar 5, 2022 at 5:51 PM Daniel Gruno <hu...@apache.org> wrote:
> >
> > If we do go down this road, the next step is to figure out how to have
> > old steve and new steve side by side. We can either keep old steve on
> > svn and make a new steve.git for the next gen product, or we can come up
> > with some sort of (code)name for this next piece of software, such as
> > steve-nextgen, steve-2, steve-buscemi etc. I don't have any good ideas
> > myself just yet. Ideas are very much welcome here!
>
> Irwin?
>

Prefontaine! Hawking! Jobs!

>

Re: Bootstrapping the next generation of STeVe

[Sam Ruby <ru...@intertwingly.net>]

On Sat, Mar 5, 2022 at 5:51 PM Daniel Gruno <hu...@apache.org> wrote:
>
> If we do go down this road, the next step is to figure out how to have
> old steve and new steve side by side. We can either keep old steve on
> svn and make a new steve.git for the next gen product, or we can come up
> with some sort of (code)name for this next piece of software, such as
> steve-nextgen, steve-2, steve-buscemi etc. I don't have any good ideas
> myself just yet. Ideas are very much welcome here!

Irwin?

- Sam Ruby

Re: Bootstrapping the next generation of STeVe

[sebb <se...@gmail.com>]

On Sat, 5 Mar 2022 at 22:51, Daniel Gruno <hu...@apache.org> wrote:
>
> Hi folks,
> As we have some renewed interest in working on STeVe, this would also be
> a good time to sort out some practicalities and names.
>
> # Version control:
> I think it would be a good move to switch to git for the next iteration.
> Not because I'm a fan of git in particular, but because of the added
> interactions with the larger community at GitHub, as well as the tools
> provided there.
>
> If we do go down this road, the next step is to figure out how to have
> old steve and new steve side by side. We can either keep old steve on
> svn and make a new steve.git for the next gen product, or we can come up
> with some sort of (code)name for this next piece of software, such as
> steve-nextgen, steve-2, steve-buscemi etc. I don't have any good ideas
> myself just yet. Ideas are very much welcome here!

What is the purpose of moving to a new generation?

[I don't count updating to Python3.]

> # Lingo etc:
> I think we're pretty fixed on using Python 3 for this next version,
> which works out great for me personally as well as our newcomer Sean.
> Front-end-wise we're probably looking at html+js with a json api or some
> such? Up for debate, do let me know what your thoughts are.
>
> # Architecture:
> TBD - I'll start some topics in separate threads on this.
>
> Anywho, these are my thoughts/questions at the moment.
>
> With regards,
> Daniel.