management - Githubissues

contao-community-alliance / composer-client

This is the Contao Composer Client

http://de.contaowiki.org/Composer

27 stars 18 forks source link

management #16

Closed dominikzogg closed 11 years ago

dominikzogg commented 11 years ago

project management: @dominikzogg repository management: @psi-4ward technical management: @tristanlins

everyone can bring ideas, code, documention...
decisions arise in discussions
we stick to the basics, which we now define

dominikzogg commented 11 years ago

What i think about:

focused on developer first, so we shouldn't do anything thats bad for devs, this means not, that we should write something crap for users (cause this was my reason to start)
many little steps in development, so we can bring features in time and tested
after the first release, also if its one to show developers how to use, we should not break compatibility until a new major version
we shouln't speak about that we have a perfect ER replacement, cause we haven't atm
this is not an official project, so until we get the permission of @leofeyer, we should only speak about an alternativ to ER and not about a replacement
this can be the base for ER3 (@tristanlins, @Discordier), but it's not atm
we should have contao lts and contao 3 support (as we have thx @tristanlins)
every one to add content, should be in authors list (code, documentattion, images...) ...

tristanlins commented 11 years ago

Personally I focused on users first, but all features developed are good for developers too ;-) I think we need some more "shorthand" features that make composer more usable for users.

A repository manager
An "Install repository from file/url" feature
An "Install package from file/url" feature
Translated composer output for non-english users

For me, the current implementation is a good start to replace the ER, but I confirm with @dominikzogg that there is more work to be done, before we can call it an "ER replacement".

You are right, this is not an official project of contao, but one of the "workgroup extension repository" and @leofeyer already knows about it and is very interested.

@Discordier and I talked about the "features" that are documented in the ER3 documentation. We will add the "missing" ones in little steps over time.

I try to bring this extension into first stable state until end of march.

At all: I would agree with @dominikzogg in almost all points. :-)

leofeyer commented 11 years ago

and @leofeyer already knows about it and is very interested

That's true. If it could become an ER replacement, I'd happily make it the official one :)

backbone87 commented 11 years ago

The biggest problem would be, to convert all existing extension to valid composer packages (e.g. create composer.json)

tristanlins commented 11 years ago

I will not provide such a feature, it's impossible! We can only provide a composer.json template.

backbone87 commented 11 years ago

You do not have to provide such a feature. I personally think it is possible, since the ER extension have a fixed layout (TL_ROOT, TL_FILES), the only problem would be outdated dependencys associations in the ER (so you can not rely on the version wildcards of composer)

leofeyer commented 11 years ago

A converter to merge the existing ER would be the cherry on the cake :)

dominikzogg commented 11 years ago

@tristanlins @backbone87 @leofeyer @psi-4ward https://github.com/ContaoCommunityAlliance/Composer/wiki

leofeyer commented 11 years ago

Does this mean you are done? :excited:

dominikzogg commented 11 years ago

@leofeyer we have a wiki, for this: https://github.com/ContaoCommunityAlliance/Composer/wiki

tristanlins commented 11 years ago

@leofeyer Yes, the discussion about management is done, the results are now in the wiki. The ER2 integration is discussed in #29