Requirements for a 1.x.y.z release

To me, we will be able to release diaspora* as 1.x when it will be possible for a non-techy person to have his own pod. That means the following points have to be easy:

• Installation
• Upgrade
• Backup
• Moderation
• Performance (a pod of 10 users should run nicely with 1GB Ram)

I have several ideas about what can be done to improve those points, I don't know if this thread is the place to discuss them on detail. There is at least one issue about admin task I opened a while ago: https://github.com/diaspora/diaspora/issues/4800

I have several ideas about what can be done to improve those points, I don’t know if this thread is the place to discuss them on detail.

It is. This is specifically its purpose, so you can go on ;)

Backup

Backup of database ? I don't think this is a realistic goal for a first release version. I'd let that one ou for a 1.0.0.0 version.

Performance (a pod of 10 users should run nicely with 1GB Ram)

Same thing here. Improve performance will be long and complicated. I don't think this should be a blocking point for a first release.

Moderation

What more, apart from what is already existing ?

It is. This is specifically its purpose, so you can go on ;)

This thread is general and I like it, I'd like to agree with everyone what should be included in 1.x. To decide about the "big picture". How we specifically solve each point should be discussed on other threads to avoid pollute this one.

1.x means diaspora* is ready to be used by the world, so, as said in my previous comment, I think the focus for 1.x should be "allow a non-techy person to have his own pod". Admin features are at this point more important to me than user features, that means, I don't think any user feature (event, group, chat...) should block 1.x.

The backup point is here because we know that hard drive can crash so it was aim to avoid private key lost.

The backup point is here because we know that hard drive can crash so it was aim to avoid private key lost.

So, this should better be automatic, than administrator-driven.

Where did you see I wanted them administrator-driven and not automatic? ;)

My personal list is more like

• Seed migration
• API
• Chat (in a usable state)
• Groups/Events
• Federation 2.0
• Redesign

ordered by importance. Especially seed migration was one of the core promises that we still couldn't deliver, releasing a 1.0 without it seems wrong. The federation point is about an iteration or redesign of the federation protocol with better stability, resilience and new standards in mind.

Federation can be interresting, indeed. Maybe you could start a discussion on what improvement you'd see in a Federation 2.0 ?

Does each one justifies a release by itself to you or all of these, or... ?

ACK @ Jonne.
That's also the list I had in mind.

The critical things for me are, sort of in order of importance:

• Seed migration, which should be simple for the end-user.
• API.
• Performance: more reliable federation, and more economical with system resources.
• Installation and maintenance of pods should be simple for the end-user, not requiring much specialist knowledge.

What constitutes an acceptable level of performance improvement or an acceptably simple installation/maintenance is a matter of debate.

Chat, groups and events, while important to a successful social network in the longer term, I would not personally consider necessary to v1.x.

Seed migration - Even in its most basic form of simply re-creating my aspects and contacts - not worried about old posts, just allow me to move pods!

I have lost count of the years I have been waiting for this core feature.