My initial design probably doesn't conform well and I was asked to reach out and develop a solution which would match the current Trac development path.
Initially I wrote my own plugin for managing ownership of whichever fields (in my case account, project, component) via a new table 'ownership' where conceivably any field could have an owner applied to a value. This plugin also allows fallback to the ownership of the previous field (eliminating generic owner Trac or no owner) when a component/project/etc is not selected. This also allowed me to add Account managers and Project managers to the CC list easily. However, I noted that the current design is for each field (so far only 1, component) to be given its own table in the DB. I have had discussion back and forth with those on my team with regards to the merit of different DB designs. As far as I can currently tell, it appears that my plugin would contradict/break the upgrade path where a future enhancement would add a table called project which matches the design of the component table. Is it preferable I continue forward with the existing structure? Are there other dependencies on components being assigned their own table? Or could it be a logical change to use an 'ownership' table (or other name) which would build on depth where each field and value/option is given its own row in a single table? I am relatively new to developing formally and even more new to developing Trac, so I am uncertain just how deeply the dependency on component having it's own table runs as well as if there is a point I am missing about DB design which makes this inherently a better design. Do you guys have opinions/preferences on which approach is better? Thanks for your responses guys! From: "RjOllos" <rjol...@gmail.com> To: "Trac Development" <trac-dev@googlegroups.com> Cc: lander...@clacorp.com Sent: Sunday, February 5, 2017 3:41:12 AM Subject: Re: Development on SimpleMultiProject On Thursday, February 2, 2017 at 11:44:14 PM UTC-8, falkb wrote: Am Donnerstag, 2. Februar 2017 17:54:48 UTC+1 schrieb RjOllos: > Do you have some preferences on the process for the community to continue > developing it? I have full confidence if you guide it a bit in the way you suggest. I just wish it'll still be cool if I update somewhen. :) CU, F@lk Thanks! So the path forward for anyone that wants to contribute is to submit some patches and I'll try to give you some feedback. If the patches look good we'll give you commit access. I have some ideas on how to better support your request for a "project" field without explicitly adding the field to Trac. I'll reply on that when I have more time to investigate. - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
