I agree. "Enhancement" was the first thing I nixed from one of my own installs of Trac, it turned into "Feature Request". Then I added "Goal" to differentiate where the request was coming from (internal, external). But really with all of that I'm just thinking out loud. I'm new, I want to contribute in some form (probably just plugins to scratch my own itches), but I don't know where the project stands, where the project is going, and what major goals exist. I like the code, I like the project, so in my copious amounts of free time, I want to give back. 'Tis all. (And I'm looking forward to it.)
Thanks again for pointing me in the right direction on the terms and vocabularies. I'll watch for changesets that introduce them into the code. Nathan Hammond On Sep 23, 6:10 pm, Arthus Erea <[EMAIL PROTECTED]> wrote: > On Sep 23, 2008, at 6:03 PM, Nathan Hammond wrote: > > > > > Hmm. There are indeed some interesting things in the schema I missed > > by looking in the wrong spots (ie. not object_terms, object_types, > > terms, and vocabularies). This looks to me like a lot of what I was > > going to do is almost outdated (MPTT and hierarchical vocabularies). I > > guess I should probably sit on this until 0.6, but I don't know > > anything about it. Is there a detailed roadmap anywhere that states > > goals? (Sorry, I know, I'm new here. I promise I looked and I can't > > find anything anywhere.) > > Owen is the best reference for this – he orchestrated the schema and > pushed it forward. > > Relevant > thread:http://groups.google.com/group/habari-dev/browse_thread/thread/dbcf58... > > > > > "The project does not make heavy use of milestones..." If there isn't > > a detailed roadmap being maintained separately Trac could be easily > > co- > > opted into handling it with milestones and a new task type, say, > > "goal." It could even organize discussions related to that "goal" in > > one nice neat little spot, provide the "Closes #XXX" functionality, a > > place to post patches, a reference for how implementation is supposed > > to work to file bugs against, and the ability to link a goal > > explicitly with changesets. Might be nice... > > Err.... that sounds a _lot_ like the "enhancement" type. Personally, I > don't think we should be attaching patches to over-arching goals. > > Honestly, I think any roadmap or feature planning should be done on > the wiki. > > I know there are some strong opinions about roadmaps. Personally, I > think it would be very valuable to have something clear-cut that we > can point at as our "plan" – even if it is really vague and general. > > > > > Then again, understand my comments to be what they are: uninformed. > > Nathan Hammond > > > On Sep 23, 5:15 pm, Arthus Erea <[EMAIL PROTECTED]> wrote: > >> No documentation has been done that I am aware of. > > >> In fact, there aren't even API hooks yet – but if you look at the > >> database schema I *think* you will see a new, more generic, terms > >> schema. > > >> On Sep 23, 2008, at 5:09 PM, Nathan Hammond wrote: > > >>> I'm now very glad I brought it up. I know naught of a new tag > >>> schema. > >>> I'm running HEAD, but the schema I'm looking at is the same as it > >>> was > >>> in the 0.5 install I had prior. Any documentation on this anywhere? > > >>> Bueller? > >>> Nathan Hammond > > >>> On Sep 23, 4:43 pm, Arthus Erea <[EMAIL PROTECTED]> wrote: > >>>> Is this using the new tag schema introduced for the 0.6 schema? > > >>>> Owen should really comment on this, but as I understand it the best > >>>> way to do this would be to create a new tag schema which actually > >>>> uses > >>>> the database hierarchy. > > >>>> I'm not sure if the core API is in place to even do that yet, but > >>>> if > >>>> its not this would probably be a good opportunity to flesh that > >>>> out. > > >>>> On Sep 23, 2008, at 4:19 PM, Nathan Hammond wrote: > > >>>>> I'm writing a plugin to support a hierarchical tagging system. > >>>>> I've > >>>>> got most all of the functionality written, I just need to hook it > >>>>> into > >>>>> Habari. > > >>>>> The basic premise is this: > >>>>> 1. User submits a piece of content with tags. The tags look > >>>>> something > >>>>> like this: > >>>>> AJAX,jQuery/plugins/Form,JavaScript > > >>>>> 2. Plugin processes the tag string with preg_replace (was faster > >>>>> than > >>>>> explode and implode) turning it into: > >>>>> AJAX,jQuery/plugins/Form,jQuery/ > >>>>> plugins,jQuery,plugins,Form,JavaScript > > >>>>> 3. Tags are inserted(/updated) based upon this string. > > >>>>> Once here everything else is essentially a display trick: > >>>>> 1. Don't display tags with a "/" in them. > >>>>> 2. When counting tags, ignore those with a "/" in them. > >>>>> 3. Add a new theme function that is able to process the list of > >>>>> tags > >>>>> into a hierarchical list. > > >>>>> I need to tap in at (three?) points: > >>>>> 1. Every time tags are inserted or updated. > >>>>> 2. Determining tag count (for dashboard). > >>>>> 3. Every time tags are output. (filter_post_tags_out? Others?) > > >>>>> Which hooks do I need? Do they exist? Help! (And thanks!) > >>>>> Nathan Hammond --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-users -~----------~----~----~----~------~----~------~--~---
