Decide on a launch date #9

Ghost commented 2022年11月06日 12:20:33 +01:00

Once the name and the organisation running the project are determined.

Once the name and the organisation running the project are determined.

Ryuno-Ki commented 2022年11月06日 12:31:42 +01:00

See also codename/website#2 (comment)

See also https://codeberg.org/codename/website/issues/2#issuecomment-667017

Ghost commented 2022年11月06日 13:48:05 +01:00

November 14th could work. But it really depends on when Codeberg explicitly agrees to host and use the fork. There seems to be an implicit agreement but given the magnitude of the project, it should be explicit before I feel comfortable moving forward. Other people may feel differently. I may need a little too much validation.

November 14th could work. But it really depends on when Codeberg explicitly agrees to host and use the fork. There seems to be an implicit agreement but given the magnitude of the project, it should be explicit before I feel comfortable moving forward. Other people may feel differently. I may need a little too much validation.

Ghost commented 2022年11月06日 17:26:02 +01:00

According to the Zen of Python

Explicit is better than implicit.

According to the Zen of Python > Explicit is better than implicit.

Gusted commented 2022年11月07日 16:57:29 +01:00

I'd rather think of MVP/Launch conditions:

• We found a suitable host and a backing org: Likely Codeberg, we just need the explicit agreement.
• Have a CoC in place: We are still casting votes on this.
• We can market the software(I know, this sounds very business): We need a website.
  • Social media handles.
• Decided on the name: @fr33domlover is taking care of this ❤️.
• Figure out a good workflow which would make a soft-fork happen: @dachary and I would likely work on this, so far a suggestion by Loïc is to use a similair approach as the Linux kernel takes.
• Discussed the license situation: Should we move to AGPL or not.

---

We still might want to set a launch date, so there's a bit of "hurry up" by people, so we don't take too long.

I'd rather think of MVP/Launch conditions: - [ ] We found a suitable host and a backing org: Likely Codeberg, we just need the explicit agreement. - [ ] Have a CoC in place: We are still casting votes on this. - [ ] We can market the software(I know, this sounds very business): We need a website. - [ ] Social media handles. - [ ] Decided on the name: @fr33domlover is taking care of this :heart:. - [ ] Figure out a good workflow which would make a soft-fork happen: @dachary and I would likely work on this, so far a suggestion by Loïc is to use a similair approach as the Linux kernel takes. - [ ] Discussed the license situation: Should we move to AGPL or not. ---- We still might want to set a launch date, so there's a bit of "hurry up" by people, so we don't take **too** long.

Ghost commented 2022年11月07日 17:46:55 +01:00

I think the launch conditions are listed in the launch milestone. But you mention a few additional points:

Social media handles.

@caesar mentioned it and I forgot to create a task for it. Here it is codename/meta#21

Figure out a good workflow which would make a soft-fork happen:

Does this need to be decided before launch or can it be done after?

Discussed the license situation: Should we move to AGPL or not.

I'm convinced this should be tabled for after the launch. I wrote down why elsewhere but can't remember where right now 😓

I think the launch conditions are listed in [the launch milestone](https://codeberg.org/codename/meta/milestone/2788). But you mention a few additional points: > Social media handles. @caesar mentioned it and I forgot to create a task for it. Here it is https://codeberg.org/codename/meta/issues/21 > Figure out a good workflow which would make a soft-fork happen: Does this need to be decided before launch or can it be done after? > Discussed the license situation: Should we move to AGPL or not. I'm convinced this should be tabled for after the launch. I wrote down why elsewhere but can't remember where right now :sweat:

Gusted commented 2022年11月07日 18:10:15 +01:00

Does this need to be decided before launch or can it be done after?

Preferably before launch, but given its the two of us, we can do it in parallel with other some other "major" task.

I'm convinced this should be tabled for after the launch. I wrote down why elsewhere but can't remember where right now 😓

I'm only bringing it up, as other people(read developers) are bringing it up to me. Which indicates it could be a "selling point" at launch for developers to take a look and contribute to a soft fork.

> Does this need to be decided before launch or can it be done after? Preferably before launch, but given its the two of us, we can do it in parallel with other some other "major" task. > I'm convinced this should be tabled for after the launch. I wrote down why elsewhere but can't remember where right now 😓 I'm only bringing it up, as other people(read developers) are bringing it up to me. Which indicates it could be a "selling point" at launch for developers to take a look and contribute to a soft fork.

Ghost commented 2022年11月07日 19:06:22 +01:00

Preferably before launch, but given its the two of us, we can do it in parallel with other some other "major" task.

You're right. I added a task in the Launch milestone for that purpose codename/meta#22

> Preferably before launch, but given its the two of us, we can do it in parallel with other some other "major" task. You're right. I added a task in the Launch milestone for that purpose https://codeberg.org/codename/meta/issues/22

Ryuno-Ki commented 2022年11月07日 21:05:06 +01:00

• We can market the software(I know, this sounds very business): We need a website.
  • Social media handles.
  • And a mascot. For mugs and shirts and stickers!

Fixed that for ya :)

> - [ ] We can market the software(I know, this sounds very business): We need a website. > - [ ] Social media handles. > - [ ] And a mascot. For mugs and shirts and stickers! Fixed that for ya :)

Gusted commented 2022年11月07日 21:06:18 +01:00

Yeah mascot depends on the name, but @circlebuilder already has a "clear" mind about this, if we choose "Smithy".

Yeah mascot depends on the name, but @circlebuilder already has a "clear" mind about this, if we choose "Smithy".

Ghost commented 2022年11月08日 09:08:06 +01:00

As discussed this morning in the chat, it would be worth deciding on a launch interval to take into account the fact that the launch has a time sensitive aspect to it. If done later (six months from now):

• less people will notice
• less people will be motivated to work on the fork

I'm inclined to think that some time between December 1st and December 15th is a good target. Enough time to complete the required tasks and not so far away in the future so that people involved (me included) are still highly motivated. A good balance between being quick and being prepared.

As discussed this morning in the chat, it would be worth deciding on a launch interval to take into account the fact that the launch has a time sensitive aspect to it. If done later (six months from now): * less people will notice * less people will be motivated to work on the fork I'm inclined to think that some time between December 1st and December 15th is a good target. Enough time to complete the [required tasks](https://codeberg.org/codename/meta/milestone/2788) and not so far away in the future so that people involved (me included) are still highly motivated. A good balance between being quick and being prepared.

Ghost commented 2022年11月08日 10:06:48 +01:00

@circlebuilder if I'm not mistaken you think that launching after December 15th may be a little late. Not too late but people's attention won't be the same. Right?

@circlebuilder if I'm not mistaken you think that launching after December 15th may be a little late. Not too late but people's attention won't be the same. Right?

Ryuno-Ki commented 2022年11月08日 10:38:10 +01:00

After 15th December, minds will surely be in christmas mode.

After 15th December, minds will surely be in christmas mode.

caesar commented 2022年11月08日 11:46:00 +01:00

On Matrix I suggested a potential 'phased' launch which might help relieve pressure / prioritise tasks:

Another way to look at this is to divide it into a "soft launch" and a "public launch".

Soft launch depends on having a name, community guidelines, and strategy. At this point we can start quietly talking about it to the "right" people – people we think might want to get involved. No releases or anything like that yet. Just getting more people on board and gathering steam.

Public launch would depend on everything currently in the Launch milestone - in particular, branding, website, and release builds ready. At this point we can start actively publicising it.

[On Matrix](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/79ドルX5nRZAyvGeHPNVg5aHoP9aFfecz1MYGGUWX8J_cbA) I suggested a potential 'phased' launch which might help relieve pressure / prioritise tasks: > Another way to look at this is to divide it into a "soft launch" and a "public launch". > > Soft launch depends on having a name, community guidelines, and strategy. At this point we can start quietly talking about it to the "right" people – people we think might want to get involved. No releases or anything like that yet. Just getting more people on board and gathering steam. > > Public launch would depend on everything currently in the [Launch milestone](https://codeberg.org/codename/meta/milestone/2788) - in particular, branding, website, and release builds ready. At this point we can start actively publicising it.

Ghost commented 2022年11月08日 11:58:22 +01:00

In the same spirit it could be thought of as a continuous soft launch. As tasks are accomplished (such as picking a name) it becomes more and more concrete. Talking about Smithy instead of codename. Then talking about Codeberg instead of "an organization" etc.

Each task is a kind of phase in its own right. When it is completed, we level up towards the launch.

In the same spirit it could be thought of as a continuous soft launch. As tasks are accomplished (such as picking a name) it becomes more and more concrete. Talking about Smithy instead of codename. Then talking about Codeberg instead of "an organization" etc. Each task is a kind of phase in its own right. When it is completed, we level up towards the launch.

Ghost commented 2022年11月08日 13:04:39 +01:00

Since there seems to be an consensus that launching after December 15th, I set that as a date for the launch milestone. Nothing prevents launching earlier if everything is ready.

If anyone disagrees, feel free to re-open this issue and discuss this further.

Since there seems to be an consensus that launching after December 15th, I set that as a date for the [launch milestone](https://codeberg.org/codename/meta/milestone/2788). Nothing prevents launching earlier if everything is ready. If anyone disagrees, feel free to re-open this issue and discuss this further.

Ryuno-Ki commented 2022年11月08日 15:52:54 +01:00

When it is completed, we level up towards the launch.

Gamification at its best 🍄

> When it is completed, we level up towards the launch. Gamification at its best 🍄

Ghost commented 2022年11月10日 23:40:09 +01:00

I did not actually close the issue, I'm doing that now since there has been no objection so far. Please re-open if you think differently.

I did not actually close the issue, I'm doing that now since there has been no objection so far. Please re-open if you think differently.

sanjibukai commented 2022年11月11日 00:50:44 +01:00

After 15th December, minds will surely be in christmas mode.

December 1st we'll all be in AoC scratching our heads 😉

> After 15th December, minds will surely be in christmas mode. December 1st we'll all be in AoC scratching our heads 😉

forgejo/meta