Using NodeBB for Project Management
-
@tradingdojo lots of people come in with ideas for what this platform could do; you're not the first, and certainly not the last.
I think that @pichalite's (somewhat salty, imo) response is that a lot of requests come in like this, but are detrimental to the core project, either as a distraction from what the software is supposed to do, or a feature that only a few people will use.
I've been at a company where feature bloat was a cancer in the product, and was a major factor in why it was hard to implement a lot of things easily. I really respect that this team judiciously chooses to leave things out of core and build everything as a plugin (which has its own problems) but it essentially avoids the scenario where person A has to deal with all the feature bloat that they won't use because person X really needed feature Y.
However, the great thing about this business model is, it's open source and free for you to hack on, so no one will stop you from using it as a project management system. I do agree with pichalite that effort is probably better spent using something that's designed more for your purpose (trello, quip, confluence comes to mind), but it's up to you.
-
@psychobunny is all like
-
Damnit that's technically off topic so does this mean I have to ban you?
My two cents: am interested to know how this goes. If it ends up being something pretty legit you might just find backing from somewhere...
-
where is the option to ban @psychobunny
-
@psychobunny said in Using NodeBB for Project Management:
My two cents: am interested to know how this goes. If it ends up being something pretty legit you might just find backing from somewhere...
Thanks for having an open mind. The initial idea to tailor the NodeBB interface towards project management and the follow up concept to embed an outline with collapsible bullets are technically competing tools to accomplish the same goal. The goal being flexible manipulation of written ideas for the development of efficient processes.
The process of developing processes needs to be as smooth as possible. I can go into a state where ideas are flowing rapidly, the next one feeding off the last. If I were to stop and focus on just one of them, to gauge its ideal home in the core model, it would disrupt the flow. Walking away can help at times but I cannot deny the many times the best idea hit me at the very end of a 4hr session. Collapsible subtasks make it possible to go on these creative runs and then initiate the organization phase where we summarize through abstract thinking and put things in there proper places. Being able to do all of this in a transparent way, using forum software, kills two birds with one stone. Your team can challenge with alternative solutions, until we've exhausted optimization options.
Attempting to best the current effectiveness of pm solutions may seem pointless. It may or may not be but we must not fear failure. Confirming something is not worth pursuing is typically the best bet. Assuming it, on the other hand, is a fear based approach. Ironically, being too conservative with time can be the riskier position
The creative process is a mission oriented problem solving competition that scales all obstacles.
-
This is a great idea!
-
Place a link to a moo.do outline in the original post. Presto, integration without really integrating the code. Even this half baked setup is superior to all dedicated pm solutions that I have tried. For me, efficiency is the primary factor when evaluating software. How quickly we can download the data we need and upload our input. Number of clicks is a useful metric.
Having every resource available on the home page is a highly efficient design for a workflow tool. I view nodebb as the best version of this concept.
Its easy to recommend the popular product. Actually testing all of them to isolate value is challenging. Try not to anchor yourself until you've done the research.
