Jamulus
Project management #1131
Replies: 5 comments 23 replies
-
|
It will help organize issues into related milestones. |
Beta Was this translation helpful? Give feedback.
-
|
Great! I will give you access in a few minutes. |
Beta Was this translation helpful? Give feedback.
-
|
Done |
Beta Was this translation helpful? Give feedback.
-
|
One thing that came up in discussion was a "roadmap" of some kind. I've had a look around on other FOSS and similar projects and there's a lot of wide variation in the concepts. @gene96817 is that what you mean my "milestones"? I was wondering whether we might have "Current phase", "Next Phase", "Future phases"? So a bit like Debian's Stable, Testing, Unstable conceptions, only we'd not have builds, just feature priorities, and not date driven. |
Beta Was this translation helpful? Give feedback.
-
I think solving the problem needs to be a priority. I don't know of a solution, though. So yes, more work is needed before a clear solution can be written up - as far as I'm aware.
Hm. Maybe I was over-thinking the problem at the time. If you don't consider anything but mixer channels, you could always alert if the mixer changed. So there would need to be a setting to enable this for those who can see such alerts but not the mixer. (I was thinking of having the server push a notification when someone joined or left - but the effect is that the mixer changes at the client, of course, so the client can work it out.)
For people who didn't want it, there would be. So it would need to be a server UI and command line option, plus the support to pass that into the recorder start up. Again, I've not heard it being a problem for many people, so I'd expect the default to be UTC as it is now. My experience with time zones is that they make code obscure and hard to maintain... |
Beta Was this translation helpful? Give feedback.
-
That was raised as a discussion before Github had them, I think. It also spawned about three or four branches off master, IIRC... It's not "finished"..! (It doesn't have any completion criteria...) |
Beta Was this translation helpful? Give feedback.
-
|
OK will record that in the sheet. Oh BTW once we're down to a solid list of actionable stuff in the issues (that is, fairly clear things to go and work on) I was going to ask: what do we think of the idea of adopting a convention of editing the "base" ticket in response to comments on it? This would be so that if someone wanted to pick something up, they'd have a decent summary of the current thinking available without having to read through all the comments to work it out. |
Beta Was this translation helpful? Give feedback.
-
|
BTW also today I'll start the process of closing out and moving various issues to discussion. |
Beta Was this translation helpful? Give feedback.
-
|
OK done that - mostly. I ended up taking a fairly conservative approach and left some pending a bit more info from the posters - in some cases it looked like they might be on the verge of being able to spec them up. Also BTW while I know that some are obviously in the "never going to happen" category, I thought it best to move them to Also interesting to see that the act of moving things to discussion has brought back some from the dead. The metronome redux! This then leaves most things in Issues as at least reasonably stable descriptions but in many cases seemingly dormant. Might need to do a second pass over those now. |
Beta Was this translation helpful? Give feedback.
-
|
One reason I suggested this process was that it appeared to me that we were addressing a lot of ideas as single stand-alone concepts. Putting some of the requests into related bundles could yield many benefits and efficiencies. |
Beta Was this translation helpful? Give feedback.
-
|
OK I'll see if I can compile a Google sheet of the issues and we can look at that. It could also be useful to help identify some general pruning and purging actions at some point so that we can get the Github Issues into a functional list and less of a bunch of blurry discussions masquerading a feature requests :-) |
Beta Was this translation helpful? Give feedback.
-
|
Great! If you want me to help out, I'll help. |
Beta Was this translation helpful? Give feedback.
-
|
Sheet's here https://github.com/jamulussoftware/jamuluswebsite/discussions/273#discussioncomment-377351 |
Beta Was this translation helpful? Give feedback.
-
|
@gilgongo Would you like to take a pass at grouping any of the rows by internal impact to the code? Maybe this is adding new column? Are there some obvious rows that are related by similar use cases? |
Beta Was this translation helpful? Give feedback.
-
|
The first main grouping that sticks out is the UI-related stuff (as Peter has remarked in fact - although I think it's mostly for discussion in fact). There may be some other related stuff too I guess... |
Beta Was this translation helpful? Give feedback.
-
|
Moved this to the main repo since it's not only related to the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
I think #929 (reply in thread) has now taken over on this conversation so locking. |
Beta Was this translation helpful? Give feedback.
-
I think becoming more and more important to think about project management in general. Although we have the issues tab, a lot of issues are not currently being worked on. Although we have a release structure, I think, a clearer project management should be implemented. What are your thoughts?
Beta Was this translation helpful? Give feedback.
All reactions