FLOW3 Party Package

Added by Maik Hagenbruch over 6 years ago

Party Package improvements - Christian Müller

The FLOW3 Party Package fulfills the most basic requirements needed for working with person data in an application but has a lot of shortcomings. It misses any notion of relations between persons and also different parties than persons are not covered yet, as well as address data and images.

Early adopters of FLOW3 asked for more features in the Party package but it wasn't high in priority for this year so most of them implemented some sort of isolated solution for their usecase but would have appreciated if we offered some more of the basic infrastructure to manage parties.

This project aims at first collecting wishes from FLOW3 adopters about what should be added to the party package, some examples of what I already heard is in this description.

Then in a second step a development outline is to be created to show the desired (code/domain) structure.

Finally implementation of the features should take place. Together with a good documentation.

Few of the features that should go in:
Relations
Parties that are not persons (companies, organisations)
adding missing features to persons, like validation of different kind of electronic addresses (account names of different communication services)

Uses of an improved party package can be found in almost any application, from managing user profiles, to having user relations (aka „friendships“) in community style applications over to having an easy to extend base to work with addresses and organisation data.


Replies (5)

RE: FLOW3 Party Package - Added by Patrick Lobacher over 6 years ago

From my point - absolutely needed but "no money for coding" anymore - just for codesprints. So for the codesprint part +1. Perhaps it can be changed to 2 codesprints oder one longer one.

RE: FLOW3 Party Package - Added by Christian Müller over 6 years ago

Actually I think I would rather withdraw this application. Two codesprints could bring the planned changes but on the other hand by getting money for the codesprints I also have to take care of delivering the milestones. I am not sure this will finally work out. I would rather see this money added to codesprints for Flow/Neos, then I don't have any deliverables and can work on that just as time permits.

RE: FLOW3 Party Package - Added by Jo Hasenau over 6 years ago

Just for clarifiaction:

I would rather see this money added to codesprints for Flow/Neos, then I don't have any deliverables and can work on that just as time permits.

Is this a description of the attitude of the Flow/Neos team, people are currently complaining about, or could it be that it's just expressed a bit awkwardly?

Since many of the statements regarding the Flow/Neos budget applications are criticsing especially the fact, that there are no defined deliverables and milestones, it would be good if you could explain this particular sentence a bit more.

RE: FLOW3 Party Package - Added by Christian Müller over 6 years ago

Just saying that for getting two codesprints covered by the Association I will have a lot of overhead in terms of reporting milestones and invoicing and stuff like that. So to me it makes no sense really. I would then rather work on it without any constraints in terms of milestones.
If worktime would be payed I totally see the need for milestones, reporting etc. but for two small codesprints it seems like a lot of extra work is needed (as I didn't have a budget directly so far, I don't know). Hope that clarifies it.
I am not against having milestones for such a budget and in fact I tried as best as I could to lay out some for my application.

RE: FLOW3 Party Package - Added by Christian Müller over 6 years ago

And again a clarification:

I would then rather work on it without any constraints in terms of milestones. -> Which means withdrawl of the application and solely trying to do that in my spare time.

    (1-5/5)