Getting the features repo off the ground

[jcbhmr]

If/when devcontainers-community/templates#5 is merged, I think getting a first feature is a good next step. Thoughts? Should we stick to just templates for now since, as @eitsupi said: they are harder

Note that Templates and Features have a very different level of maintenance importance.
That is, Templates are only downloaded once, while Features are expected to continue to be downloaded many times in the future.

So maintenance of Features is far more important than maintenance of Templates, and when Features are handled by such an organization, the maintainer needs to be clearly stated, I think.

in my opinion I think getting a foot into both templates and features is a good way to get started.

But then again, maybe we should take it slow and focus on just the jupyter template stuff for a few more days/week (🥵 we don't want to overwork @jcbhmr and @eitsupi) before tackling anything else. Thoughts?

/cc @eitsupi

[eitsupi]

Is #5 perhaps #5 from another repository?

in my opinion I think getting a foot into both templates and features is a good way to get started.

But then again, maybe we should take it slow and focus on just the jupyter template stuff for a few more days/week (🥵 we don't want to overwork @jcbhmr and @eitsupi) before tackling anything else. Thoughts?

I think we can start with some transfers of templates from https://github.com/microsoft/vscode-dev-containers for some reasons.

• These have been in use for a while, but are now deprecated and not under maintenance.
• The scope is clear. (No possibility of unlimited increase)
• Maintenance of Templates are considered less effort than maintenance of Features. (It is the base image and the Features that are more difficult to maintain!)

Again, both Features and Templates can grow without limit unless the scope is clearly defined, and there must be clear criteria for what is to be added.

[jcbhmr]

Is #5 perhaps #5 from another repository?

Yeah lmao it was supposed to link devcontainers-community/templates#5 🤣

Again, both Features and Templates can grow without limit unless the scope is clearly defined, and there must be clear criteria for what is to be added.

You're right to think of ballooning responsibility. I think I'm being a bit overzealous. Thanks for keeping your eye on scope. 👍 I agree with your idea to stick with this:

I think we can start with some transfers of templates from https://github.com/microsoft/vscode-dev-containers

For right now, I agree that my proposal in this discussion was a bit too much and this is a better path forward for now. Thanks for moderating my enthusiasm! ❤

[eitsupi]

Your passion is really great!
However, I think we need to explore the state of sustainability to make it easier for contributors to participate.

[jcbhmr]

However, I think we need to explore the state of sustainability to make it easier for contributors to participate.

Totally key. You're right! Sticking with just that devcontainers-community/templates#5 template and making it and the docs really good seems like a good idea.

[eitsupi]

For example, as shown below, a large amount of PR can be left unattended and not good for both parties if acceptance criteria are not indicated.......
https://github.com/microsoft/vscode-dev-containers/pulls

After looking at this repository for several years, I felt it was really important to have a scope, guidelines, CI, and other standards in place.