Any wishes
-
don
- Posts: 134
- Joined: Sat Jul 18, 2015 11:03 am
- Location: Sydney, AU
Post
by don » Fri Nov 13, 2015 11:46 pm
Good day.
Should we consider using JIRA/Trac/Redmine for submitting issues? Mentioning these three as I have used them before - others might be equally good.
I believe with the tool growing popular it might come handy. It is already a bit difficult to keep track of all ideas and updates.
![Wink ;)](./images/smilies/icon_e_wink.gif)
-
darek
- Posts: 179
- Joined: Thu Jul 16, 2015 4:50 pm
- Location: Warsaw, Poland
-
Contact:
Post
by darek » Mon Nov 16, 2015 9:45 am
Actually, I was going to suggest this too. Issue tracker could be useful, but having used all those three tools, I wouldn't go overboard with any of them. Assuming that Files is targeted at pros, I'd suggest issue tracker that the most programmers and tech people are exposed to: GitHub tracker. Now, I haven't used it myself yet
![Wink ;)](./images/smilies/icon_e_wink.gif)
but it looks simple, it's certainly popular and setting it up will be easy. And later that GitHub account could be useful for other things too... Worth considering.
-
don
- Posts: 134
- Joined: Sat Jul 18, 2015 11:03 am
- Location: Sydney, AU
Post
by don » Tue Nov 17, 2015 10:15 am
Hear you.
Though GitHub power comes into play when combined with maintaining the source code there.
Anyway - I am impartial to what it is as far there is something like that
![Smile :)](./images/smilies/icon_e_smile.gif)
-
don
- Posts: 134
- Joined: Sat Jul 18, 2015 11:03 am
- Location: Sydney, AU
Post
by don » Sun Nov 22, 2015 4:43 am
Also, would be helpful to get a wiki somewhere too.
We the development pace like this new features introduced quite quickly.
Would be nice to be able to document them somewhere visible to a wider audience.
-
mike
- Posts: 1060
- Joined: Thu Jul 16, 2015 5:35 am
- Location: Exeter, UK
Post
by mike » Wed Nov 25, 2015 4:16 am
Guys,
Good point.
I'll open an issue tracker on GitHub, since I use it already anyway.
Having a Wiki is good idea too, I'll start writing it some day.
Mike.
-
don
- Posts: 134
- Joined: Sat Jul 18, 2015 11:03 am
- Location: Sydney, AU
Post
by don » Sat Nov 28, 2015 7:40 am
For the wiki - it might make sense to let other people contribute too.
Myself I would definitely pick the answers for my questions and put them on the wiki somewhere - just for the future reference myself.
Collaborative environment, see.
-
mike
- Posts: 1060
- Joined: Thu Jul 16, 2015 5:35 am
- Location: Exeter, UK
Post
by mike » Wed Jun 15, 2016 7:53 am
Friends,
I've moved most of tasks in my private issue tracker to a public one:
https://github.com/mikekazakov/nimble-commander/issues
This URL surely looks badly, but I don't know if GitHub allows any domain substitution for it's main functionality (GitHub Pages allows only static content).
It's quite a fresh tracker, a lot of ideas and issues mentioned here are not listed in GitHub issue tracker yet.
Any comments on integration of a public tracker into the development process are very welcome.
Also, I've placed a fresh Wiki on a website:
http://magnumbytes.com/wiki/ and will build some structure with major articles there.
Mike.
-
swoop
- Posts: 54
- Joined: Thu Mar 02, 2017 2:40 pm
- Location: Brussels, Belgium
Post
by swoop » Sat Mar 04, 2017 7:46 pm
Is there a way saying what the priority / order for upcoming implementation is?
Total Commander (Windows 95 - Windows 7) (retired for Mac)
Nimble Commander (retired Crax, Commander One, DCommander)
Macbook 12" 2016 - macOS High Sierra
-
mike
- Posts: 1060
- Joined: Thu Jul 16, 2015 5:35 am
- Location: Exeter, UK
Post
by mike » Sun Mar 05, 2017 5:14 am
At the moment there's no clear methodology in assigning features for development in some version.
Crashes first and others are flexible.