From: PCMan <pcm...@gm...> - 2013-07-26 09:51:21
|
Hello, Sorry to bother you guys with the same topic again. It's really time-consuming to do the communication stuff, but it's inevitable. It's better to have some consensus before really starting coding. While the razor guys are doing their best pushing razor-qt 0.6 as planned, I'd like to start preparing for the merge earlier. I wrote another wiki page, which is a draft for the merge and hope we can coordinate better. It also documented what we already have (but the list is not complete). http://wiki.lxde.org/en/Merge_LXDE-Qt_and_Razor-Qt Nothing is settled done yet. It's only a draft. Some are just my own opinions and I wrote them down for ease of discussion. Anything can be changed if anyone has different opinions. Feel free to add different opinions either on the wiki page or discuss in the ML. Previously we discussed about using single monolithic repo or splitting razor-qt into smaller repos. Seems that there are no objections about splitting it into smaller pieces. I'd like to know if it's the right time to do it, or we need to wait for razor-qt 0.6 release? We also need to know who is interested in working on which part so we won't duplicate the work. Regarding to the lxde side: I'll work on the file manager part and try to see if I can make a obconf qt port (openbox configuration tool). About the panel, I'm willing to work on razor-panel instead of my own poor lxpanel-qt. After I finish my file manager stuff, I'll see if there's anything I can help for razor-panel. Andriy is working on libfm and will make a new release soon. Julien is working on lxsession now. BTW, Julien, would you please document the dbus interface lxsession currently provides in the wiki? Since lxsession is currently more feature-rich than razorqt-session and it's a non-GUI program, I'd like to know if we can use lxsession and make it adopt current razorqt-session features, including the config dialogs. Or if there're objections, at least we can make lxsession and razorqt-session interchangeable first. Comments are really wanted. Thank you all. |
From: gymka <gy...@ar...> - 2013-07-26 10:49:38
|
2013.07.26 12:51, PCMan rašė: > Hello, > Sorry to bother you guys with the same topic again. I'm translator, so i'm interested only in translation:) in wiki i see "lxde-qt translation team is using own Pootle server moderated and coordinated by Martin Bagge (brother)." so there will be separate translation sites for gtk and qt versions or one?(now lxde uses .po files, qt uses .ts files; different formats, different problems) |
From: Giuseppe P. <gi...@gm...> - 2013-07-26 10:52:44
|
Hi, since I recently worked on the Keyboard Layout Handler it would be not too much effort for me to port it to the new Qt panel, just I would like to be sure that the panel will be razor-panel and not Lxde-Qt, otherwise I would prefer to wait for this decision to be definitive before starting. Cheers. On Fri, Jul 26, 2013 at 11:51 AM, PCMan <pcm...@gm...> wrote: > Hello, > Sorry to bother you guys with the same topic again. > It's really time-consuming to do the communication stuff, but it's > inevitable. > It's better to have some consensus before really starting coding. > While the razor guys are doing their best pushing razor-qt 0.6 as > planned, I'd like to start preparing for the merge earlier. > > I wrote another wiki page, which is a draft for the merge and hope we > can coordinate better. > It also documented what we already have (but the list is not complete). > > http://wiki.lxde.org/en/Merge_LXDE-Qt_and_Razor-Qt > > Nothing is settled done yet. It's only a draft. > Some are just my own opinions and I wrote them down for ease of discussion. > Anything can be changed if anyone has different opinions. > Feel free to add different opinions either on the wiki page or discuss > in the ML. > > Previously we discussed about using single monolithic repo or > splitting razor-qt into smaller repos. > Seems that there are no objections about splitting it into smaller pieces. > I'd like to know if it's the right time to do it, or we need to wait > for razor-qt 0.6 release? > > We also need to know who is interested in working on which part so we > won't duplicate the work. > Regarding to the lxde side: > I'll work on the file manager part and try to see if I can make a > obconf qt port (openbox configuration tool). > About the panel, I'm willing to work on razor-panel instead of my own > poor lxpanel-qt. After I finish my file manager stuff, I'll see if > there's anything I can help for razor-panel. > Andriy is working on libfm and will make a new release soon. > Julien is working on lxsession now. > BTW, Julien, would you please document the dbus interface lxsession > currently provides in the wiki? > > Since lxsession is currently more feature-rich than razorqt-session > and it's a non-GUI program, I'd like to know if we can use lxsession > and make it adopt current razorqt-session features, including the > config dialogs. > Or if there're objections, at least we can make lxsession and > razorqt-session interchangeable first. > Comments are really wanted. > > Thank you all. > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > |
From: PCMan <pcm...@gm...> - 2013-07-26 12:49:34
|
On Fri, Jul 26, 2013 at 6:52 PM, Giuseppe Penone <gi...@gm...> wrote: > Hi, since I recently worked on the Keyboard Layout Handler it would be not > too much effort for me to port it to the new Qt panel, > just I would like to be sure that the panel will be razor-panel and not > Lxde-Qt, otherwise I would prefer to wait for this decision to be definitive > before starting. > Cheers. There is nothing to discuss. I'm the only developer of lxpanel-qt. I decided to work on razor-panel instead. So, you have my words. Please contribute to razor-panel directly. FYI: https://github.com/Razor-qt/razor-qt/wiki/How-to-write-the-panel-plugin If you're going to port gtk+ applets to Qt, don't forget the doc. http://wiki.lxde.org/en/Migrate_from_GTK%2B_to_Qt This can save you some time. If you need any help during the porting, I'm willing to help. I'm no Qt expert, though. lol There are many good Qt programmers in the razor team. Cheers! |
From: Stephan S. <gma...@sp...> - 2013-07-26 11:03:20
|
I'm not a developer, but I would like to bring attention to a potential point of contention: The choice of a HIG and how strictly to follow it. I went to a lot of trouble to ensure OK buttons on the right-hand side of my dialogs (GNOME/OSX style) rather than Cancel buttons (Windows/KDE style) and I've never felt fully comfortable in KDE since their switch from 3.5.x to 4.0. (Regardless of other concerns, all my Qt applications use QGtkStyle because too many Qt themes I've run into have no equivalent to the gtk-alternative-button-order=0 config key.) Aside from personal taste, there are also solid, objective reasons to put OK in the right-hand corner: http://uxmovement.com/buttons/why-ok-buttons-in-dialog-boxes-work-best-on-the-right/ As for my concern with how strictly to follow the HIG, I haven't had time to read the GNOME HIG in full yet, but I find LXDE's current design to be much more comfortable than GNOME's and I worry about how many of their design decisions they may have baked into their HIG. Essentially, I'm worried that following any HIG too strictly would compromise some of the correct design decisions made in LXDE in pursuit of some less useful standard cooked up by someone with very different goals. On 13-07-26 05:51 AM, PCMan wrote: > Hello, > Sorry to bother you guys with the same topic again. > It's really time-consuming to do the communication stuff, but it's inevitable. > It's better to have some consensus before really starting coding. > While the razor guys are doing their best pushing razor-qt 0.6 as > planned, I'd like to start preparing for the merge earlier. > > I wrote another wiki page, which is a draft for the merge and hope we > can coordinate better. > It also documented what we already have (but the list is not complete). > > http://wiki.lxde.org/en/Merge_LXDE-Qt_and_Razor-Qt > > Nothing is settled done yet. It's only a draft. > Some are just my own opinions and I wrote them down for ease of discussion. > Anything can be changed if anyone has different opinions. > Feel free to add different opinions either on the wiki page or discuss > in the ML. > > Previously we discussed about using single monolithic repo or > splitting razor-qt into smaller repos. > Seems that there are no objections about splitting it into smaller pieces. > I'd like to know if it's the right time to do it, or we need to wait > for razor-qt 0.6 release? > > We also need to know who is interested in working on which part so we > won't duplicate the work. > Regarding to the lxde side: > I'll work on the file manager part and try to see if I can make a > obconf qt port (openbox configuration tool). > About the panel, I'm willing to work on razor-panel instead of my own > poor lxpanel-qt. After I finish my file manager stuff, I'll see if > there's anything I can help for razor-panel. > Andriy is working on libfm and will make a new release soon. > Julien is working on lxsession now. > BTW, Julien, would you please document the dbus interface lxsession > currently provides in the wiki? > > Since lxsession is currently more feature-rich than razorqt-session > and it's a non-GUI program, I'd like to know if we can use lxsession > and make it adopt current razorqt-session features, including the > config dialogs. > Or if there're objections, at least we can make lxsession and > razorqt-session interchangeable first. > Comments are really wanted. > > Thank you all. > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > |
From: Kevin K. <kr...@kd...> - 2013-07-26 11:11:04
Attachments:
signature.asc
|
On Friday, 2013-07-26, Stephan Sokolow wrote: > I'm not a developer, but I would like to bring attention to a potential > point of contention: The choice of a HIG and how strictly to follow it. > > I went to a lot of trouble to ensure OK buttons on the right-hand side > of my dialogs (GNOME/OSX style) rather than Cancel buttons (Windows/KDE > style) and I've never felt fully comfortable in KDE since their switch > from 3.5.x to 4.0. That shouldn't be a problem in Qt applications or at least not if the developers are using QDialogButtonBox as recommended. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring |
From: Stephan S. <gma...@sp...> - 2013-07-26 11:47:31
|
The problem isn't in the applications. The problem is that many themes force KDE/Windows button order. I was using it both as a caution about that problem and as an example of how "little changes" can matter a lot, so any changes to come into compliance with a HIG should be made with extreme caution. On 13-07-26 07:10 AM, Kevin Krammer wrote: > On Friday, 2013-07-26, Stephan Sokolow wrote: >> I'm not a developer, but I would like to bring attention to a potential >> point of contention: The choice of a HIG and how strictly to follow it. >> >> I went to a lot of trouble to ensure OK buttons on the right-hand side >> of my dialogs (GNOME/OSX style) rather than Cancel buttons (Windows/KDE >> style) and I've never felt fully comfortable in KDE since their switch >> from 3.5.x to 4.0. > > That shouldn't be a problem in Qt applications or at least not if the > developers are using QDialogButtonBox as recommended. > > Cheers, > Kevin > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > > |
From: Andrej N. G. <an...@re...> - 2013-07-26 11:44:53
|
Hello! PCMan has written on Friday, 26 July, at 17:51: >Sorry to bother you guys with the same topic again. >It's really time-consuming to do the communication stuff, but it's inevitable. >It's better to have some consensus before really starting coding. >While the razor guys are doing their best pushing razor-qt 0.6 as >planned, I'd like to start preparing for the merge earlier. >I wrote another wiki page, which is a draft for the merge and hope we >can coordinate better. >It also documented what we already have (but the list is not complete). >http://wiki.lxde.org/en/Merge_LXDE-Qt_and_Razor-Qt What bothers me in that article is the sentence "Currently github is more favored." We all discussed that github is a temporary solution... I hate github really, it is very inconvenient in some aspects and their "issue tracker" is poor at the best. I hardly have any desire to work with that "issue tracker", the same way as some developers ignore the SF one. Well, if you go back and want github not as temporary solution but as main host for the project, I will not go agaisnt you but I will be set to find a solution for code that I work with. For GIT web interface I have a solution - I just install the GitWeb on one of my websites and will use it, pushing code time to time into your loved github, but github's "issue tracker" will never have my love so I will rarely come there and answer any questions, that will be all your job. I'm sorry. >Nothing is settled done yet. It's only a draft. >Some are just my own opinions and I wrote them down for ease of discussion. >Anything can be changed if anyone has different opinions. >Feel free to add different opinions either on the wiki page or discuss >in the ML. In panel applets list few very requested ones are missing: - keyboard layout display/switcher - directories menu - weather/forecast applet Cheers! Andriy. |
From: Andrej N. G. <an...@re...> - 2013-07-27 18:21:22
|
Hello! PICCORO McKAY Lenz has written on Saturday, 27 July, at 13:19: >On Sat, Jul 27, 2013 at 10:01 AM, Jerome Leclanche <ad...@gm...>wrote: >> 3. Project will be on GithuB, BitBucket, SF? >> Github and mirrored on SF. >>> why not bitBuicket, has a web interface more cleaner and works with >light webbrowsers.. currently github has a lot of js process in background >when loading and need modern web browsers >and most important, github works bad with icecat GNU web browser... Free bug tracker of the bitbucket is very poor. Well, it may be a bit better than one of github, but it is still very poor even comparing with sourceforge one - no milestones, no categories... And more advanced one (named JIRA) is not free. Well, it may be just me who wants a convenient tracker anyway and everyone else either ignore bugs or dig thru all of them always, filtering nothing. But at work we never would work with such simplified system, just because at work we have a team and such primitive trackers never work for a team but only for some private projects. Cheers! Andriy. |
From: PICCORO M. L. <mck...@gm...> - 2013-07-27 20:59:13
|
On Sat, Jul 27, 2013 at 1:51 PM, Andrej N. Gritsenko <an...@re...>wrote: > Free bug tracker of the bitbucket is very poor. Well, it may be a bit > better than one of github thast the point, are bit better rather than github.. ok team support and group tasking are not supported in bitbucket, but at least work with my lenny current installeed browsers I wish we had a system like redmine at least... but well > But at work we never would work with such > simplified system, just because at work we have a team and such primitive > trackers never work for a team but only for some private projects. > so i miss the point, then, where will work the buctraker and tracker of roadmap? |
From: Martin B. / b. <br...@bs...> - 2013-07-29 15:55:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2013-07-27 22:59, PICCORO McKAY Lenz wrote: > so i miss the point, then, where will work the buctraker and > tracker of roadmap? This is not decided yet. You haven't missed the point, maybe you just need to slow down =) - -- brother http://sis.bthstudent.se -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBCAAGBQJR9pCFAAoJEJbdSEaj0jV7qXoH/Aqsz4lJbbrOHo5CkCx3mpLb lVY7kj44vrZmldw9eDynfxrOaK28FNYF453a+oKGAQ6xJREqWs2ydmn947tvAPMa lYrp/DPnurghge/EpIuX/qaKRkm0OX3jB9u+Gk0UAESdBvqAlRwcsXW7Xq4iL6KA sUr0n9u6aJalirkct+MA6JLzL8K81bFtFuQOeir9bB2GmVsqSbQR69GbwKpUb+et WUW0Ge5csKZgkhE0vqcd4NoP7UKAuQfcwyy8PuxlDLklLH8uq1ljfaxXlIeKtmK0 KSDyn1XweP9R4MQkwcCmheHtCvIUJ0wVO4ylAJXQYUyOb2PiQEwHWgkxpm3Eg1E= =oDmk -----END PGP SIGNATURE----- |
From: Veeti P. <vee...@ro...> - 2013-07-28 21:14:37
|
On 27/07/13 21:21, Andrej N. Gritsenko wrote: > Free bug tracker of the bitbucket is very poor. Well, it may be a bit > better than one of github, but it is still very poor even comparing with > sourceforge one - no milestones, no categories... And more advanced one > (named JIRA) is not free. Well, it may be just me who wants a convenient > tracker anyway and everyone else either ignore bugs or dig thru all of > them always, filtering nothing. But at work we never would work with such > simplified system, just because at work we have a team and such primitive > trackers never work for a team but only for some private projects. It may be worth mentioning that JIRA licenses are free for open-source projects: https://www.atlassian.com/software/views/open-source-license-request |
From: PCMan <pcm...@gm...> - 2013-07-29 01:46:48
|
On Mon, Jul 29, 2013 at 4:49 AM, Veeti Paananen <vee...@ro...> wrote: > On 27/07/13 21:21, Andrej N. Gritsenko wrote: >> Free bug tracker of the bitbucket is very poor. Well, it may be a bit >> better than one of github, but it is still very poor even comparing with >> sourceforge one - no milestones, no categories... And more advanced one >> (named JIRA) is not free. Well, it may be just me who wants a convenient >> tracker anyway and everyone else either ignore bugs or dig thru all of >> them always, filtering nothing. But at work we never would work with such >> simplified system, just because at work we have a team and such primitive >> trackers never work for a team but only for some private projects. > > It may be worth mentioning that JIRA licenses are free for open-source > projects: > > https://www.atlassian.com/software/views/open-source-license-request > Only if you do advertisement for them. You have to install a trial version on your website and make it available to the public. Using kde IMO is better than this. |
From: Andrej N. G. <an...@re...> - 2013-07-26 13:23:23
|
Hello! Giuseppe Penone has written on Friday, 26 July, at 12:52: >Hi, since I recently worked on the Keyboard Layout Handler it would be not >too much effort for me to port it to the new Qt panel, >just I would like to be sure that the panel will be razor-panel and not >Lxde-Qt, otherwise I would prefer to wait for this decision to be >definitive before starting. While you are working on it, I would like to take your attention about switching selection - it currently has only single choice but it would be much better if it could have multiple, for example: switch by right control, and temporary switch by right alt, and indicate with the "scroll lock" LED. The indication is completely missed in the choices with this obvious reason of single selection so it would be very good to have it there too. >Cheers. Cheers! Andriy. |
From: Giuseppe P. <gi...@gm...> - 2013-07-26 13:28:30
|
Hello Andriy, in the new version I'll add those options If I will be able to :) Cheers, Giuseppe. On Fri, Jul 26, 2013 at 3:23 PM, Andrej N. Gritsenko <an...@re...>wrote: > Hello! > > Giuseppe Penone has written on Friday, 26 July, at 12:52: > >Hi, since I recently worked on the Keyboard Layout Handler it would be not > >too much effort for me to port it to the new Qt panel, > >just I would like to be sure that the panel will be razor-panel and not > >Lxde-Qt, otherwise I would prefer to wait for this decision to be > >definitive before starting. > > While you are working on it, I would like to take your attention > about switching selection - it currently has only single choice but it > would be much better if it could have multiple, for example: switch by > right control, and temporary switch by right alt, and indicate with the > "scroll lock" LED. The indication is completely missed in the choices > with this obvious reason of single selection so it would be very good to > have it there too. > > >Cheers. > > Cheers! > Andriy. > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Lxde-list mailing list > Lxd...@li... > https://lists.sourceforge.net/lists/listinfo/lxde-list > |
From: PICCORO M. L. <mck...@gm...> - 2013-07-26 13:30:30
|
*what about bitbucket *? the web interface are more light and do not have too many js process in background... issue tracker seems more avanced rather than github... On Fri, Jul 26, 2013 at 7:14 AM, Andrej N. Gritsenko <an...@re...>wrote: > What bothers me in that article is the sentence "Currently github is > more favored." We all discussed that github is a temporary solution... I > hate github really, it is very inconvenient in some aspects and their > "issue tracker" is poor at the best. I hardly have any desire to work > with that "issue tracker", the same way as some developers ignore the SF > one. > i really hate github and sf due the web interface, use a lot of js that make my browser consumes lot of memory.. and some thing do not work due "u need to upgrade u'r browser" rule... > Well, if you go back and want github not as temporary solution but as > main host for the project, I will not go agaisnt you but I will be set to > find a solution for code that I work with. For GIT web interface I have a > solution - I just install the GitWeb on one of my websites and will use > as i said.. and then this seems a good solution if plans are use github.. > it, pushing code time to time into your loved github, but github's "issue > tracker" will never have my love so I will rarely come there and answer > any questions, that will be all your job. I'm sorry. > i agree In panel applets list few very requested ones are missing: > - keyboard layout display/switcher > - directories menu > - weather/forecast applet > |
From: Stephan S. <gma...@sp...> - 2013-07-26 14:04:36
|
It'd make sense for it to be more advanced. As I understand it, it's a simplified frontend to JIRA and I'd be very surprised if they pared something as featureful as JIRA down as far as GitHub Issues. I don't really mind BitBucket too much. It's nicer and more featureful than Google Code, less annoying than SourceForge, and the main ways it falls short of GitHub are things that don't apply here. For example, LXDE already has its own hosting, so their lack of a GitHub Pages equivalent (last I checked) isn't an issue. They do apply a spam filter to even the logged-in bug tracker posts (Akismet, I think) and that's bitten me once or twice, but it's probably not a huge issue, and their assumption that e-mail bug replies will come from a From: address known to their system is a weakness, but I never trust bug replies without a preview so I don't use that anyway. Having the option of logging in using OpenID or using an existing GitHub account as an OAuth provider to sign in is also a plus. On 13-07-26 09:30 AM, PICCORO McKAY Lenz wrote: > *what about bitbucket *? the web interface are more light and do not > have too many js process in background... issue tracker seems more > avanced rather than github... > > On Fri, Jul 26, 2013 at 7:14 AM, Andrej N. Gritsenko <an...@re... > <mailto:an...@re...>> wrote: > > What bothers me in that article is the sentence "Currently > github is > more favored." We all discussed that github is a temporary solution... I > hate github really, it is very inconvenient in some aspects and their > "issue tracker" is poor at the best. I hardly have any desire to work > with that "issue tracker", the same way as some developers ignore the SF > one. > > i really hate github and sf due the web interface, use a lot of js that > make my browser consumes lot of memory.. and some thing do not work due > "u need to upgrade u'r browser" rule... > > Well, if you go back and want github not as temporary solution > but as > main host for the project, I will not go agaisnt you but I will be > set to > find a solution for code that I work with. For GIT web interface I > have a > solution - I just install the GitWeb on one of my websites and will use > > as i said.. and then this seems a good solution if plans are use github.. > > it, pushing code time to time into your loved github, but github's > "issue > tracker" will never have my love so I will rarely come there and answer > any questions, that will be all your job. I'm sorry. > > i agree > > > In panel applets list few very requested ones are missing: > - keyboard layout display/switcher > - directories menu > - weather/forecast applet > > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > > |
From: Stephan S. <gma...@sp...> - 2013-07-28 02:13:01
|
On 13-07-27 02:21 PM, Andrej N. Gritsenko wrote: > better than one of github, but it is still very poor even comparing with > sourceforge one - no milestones, no categories... And more advanced one I can understand your viewpoint but keep in mind that I have a pile of bugs kicking around somewhere in the TiddlyWiki I use as a PIM tool which I haven't reported because the end user experience for the SourceForge tracker is so bad that I've procrastinated visiting it so long that, instead, I'm now procrastinating the process of verifying whether they are still a problem. ...plus, the fact that SourceForge automatically closes bugs that have lain dormant for too long is a major discouragement and smacks of assuming that everyone wants the CADT model. http://www.jwz.org/doc/cadt.html |
From: Andrej N. G. <an...@re...> - 2013-07-28 10:17:48
|
Hello! Stephan Sokolow has written on Saturday, 27 July, at 22:12: >...plus, the fact that SourceForge automatically closes bugs that have >lain dormant for too long is a major discouragement and smacks of >assuming that everyone wants the CADT model. First, SourceForge closed the bugs only marked as Pending, not Open ones. Second, it doesn't do that for long enough time, I marked few bugs as Pending last year and they were never closed. I suppose they got few requests to disable the feature so they've disabled it. Cheers! Andriy. |
From: Stephan S. <gma...@sp...> - 2013-07-28 10:36:51
|
Hmm. Well, in that case, I suppose my only complaint is that I find even Bugzilla to have a more comfortable UI than SourceForge's issue tracker. (Bugzilla may have quite the learning curve, but once I got used to it, I found it comfortable. SourceForge's issue tracker just never seems to get comfortable.) However, keep in mind that, by bringing my mistaken assumption to your attention so you could correct it, I've become part of a small minority of users. Unless SourceForge somehow makes a clean break between whatever they currently offer and their old bug tracker in peoples' minds, it's a problem that's going to drag on willingness to participate among potential new community members. (The "if you need to personally respond to clarify/correct something", then the solution is broken because there will be many others who are affected and don't contact you about it." principle.) On 13-07-28 06:17 AM, Andrej N. Gritsenko wrote: > Hello! > > Stephan Sokolow has written on Saturday, 27 July, at 22:12: >> ...plus, the fact that SourceForge automatically closes bugs that have >> lain dormant for too long is a major discouragement and smacks of >> assuming that everyone wants the CADT model. > > First, SourceForge closed the bugs only marked as Pending, not Open > ones. Second, it doesn't do that for long enough time, I marked few bugs > as Pending last year and they were never closed. I suppose they got few > requests to disable the feature so they've disabled it. > > Cheers! > Andriy. > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > |
From: PCMan <pcm...@gm...> - 2013-07-28 11:10:02
|
On Sun, Jul 28, 2013 at 6:36 PM, Stephan Sokolow <gma...@sp...> wrote: > Hmm. Well, in that case, I suppose my only complaint is that I find even > Bugzilla to have a more comfortable UI than SourceForge's issue tracker. > > (Bugzilla may have quite the learning curve, but once I got used to it, > I found it comfortable. SourceForge's issue tracker just never seems to > get comfortable.) > > However, keep in mind that, by bringing my mistaken assumption to your > attention so you could correct it, I've become part of a small minority > of users. > > Unless SourceForge somehow makes a clean break between whatever they > currently offer and their old bug tracker in peoples' minds, it's a > problem that's going to drag on willingness to participate among > potential new community members. > > (The "if you need to personally respond to clarify/correct something", > then the solution is broken because there will be many others who are > affected and don't contact you about it." principle.) > > On 13-07-28 06:17 AM, Andrej N. Gritsenko wrote: >> Hello! >> >> Stephan Sokolow has written on Saturday, 27 July, at 22:12: >>> ...plus, the fact that SourceForge automatically closes bugs that have >>> lain dormant for too long is a major discouragement and smacks of >>> assuming that everyone wants the CADT model. >> >> First, SourceForge closed the bugs only marked as Pending, not Open >> ones. Second, it doesn't do that for long enough time, I marked few bugs >> as Pending last year and they were never closed. I suppose they got few >> requests to disable the feature so they've disabled it. >> >> Cheers! >> Andriy. I'm going to attend an open source conference and give a speech on Aug 3. People from our local open source communities will go there and I'll meet some friends there. If I can find someone to host bugzilla for us, I mean our own server, is this acceptable for you guys? |
From: PCMan <pcm...@gm...> - 2013-07-26 14:34:46
|
On Fri, Jul 26, 2013 at 10:04 PM, Stephan Sokolow <gma...@sp...> wrote: > It'd make sense for it to be more advanced. As I understand it, it's a > simplified frontend to JIRA and I'd be very surprised if they pared > something as featureful as JIRA down as far as GitHub Issues. > > I don't really mind BitBucket too much. It's nicer and more featureful > than Google Code, less annoying than SourceForge, and the main ways it > falls short of GitHub are things that don't apply here. > > For example, LXDE already has its own hosting, so their lack of a GitHub > Pages equivalent (last I checked) isn't an issue. > > They do apply a spam filter to even the logged-in bug tracker posts > (Akismet, I think) and that's bitten me once or twice, but it's probably > not a huge issue, and their assumption that e-mail bug replies will come > from a From: address known to their system is a weakness, but I never > trust bug replies without a preview so I don't use that anyway. > > Having the option of logging in using OpenID or using an existing GitHub > account as an OAuth provider to sign in is also a plus. > > On 13-07-26 09:30 AM, PICCORO McKAY Lenz wrote: >> *what about bitbucket *? the web interface are more light and do not >> have too many js process in background... issue tracker seems more >> avanced rather than github... >> >> On Fri, Jul 26, 2013 at 7:14 AM, Andrej N. Gritsenko <an...@re... >> <mailto:an...@re...>> wrote: >> >> What bothers me in that article is the sentence "Currently >> github is >> more favored." We all discussed that github is a temporary solution... I >> hate github really, it is very inconvenient in some aspects and their >> "issue tracker" is poor at the best. I hardly have any desire to work >> with that "issue tracker", the same way as some developers ignore the SF >> one. >> >> i really hate github and sf due the web interface, use a lot of js that >> make my browser consumes lot of memory.. and some thing do not work due >> "u need to upgrade u'r browser" rule... >> >> Well, if you go back and want github not as temporary solution >> but as >> main host for the project, I will not go agaisnt you but I will be >> set to >> find a solution for code that I work with. For GIT web interface I >> have a >> solution - I just install the GitWeb on one of my websites and will use >> >> as i said.. and then this seems a good solution if plans are use github.. >> >> it, pushing code time to time into your loved github, but github's >> "issue >> tracker" will never have my love so I will rarely come there and answer >> any questions, that will be all your job. I'm sorry. >> >> i agree >> Bitbucket has one waek point. It's a paid service. Free users have many limitations. If we're going to use it, then we probably need some sponsor to pay for it. |
From: Stephan S. <gma...@sp...> - 2013-07-26 14:44:40
|
Last I looked into them, they seemed to be on essentially the same model as GitHub (everything free for public repos, pay for private ones) with the main difference being that BitBucket doesn't require you to pay if your private repos are shared between 5 or fewer users. (as an attempt to compete with GitHub's huge popularity) Their "Plans" page isn't exactly clear, but that still seems to be the case. You get "5 users" for free and a user is "someone with access to one of your PRIVATE repos". On 13-07-26 10:34 AM, PCMan wrote: > On Fri, Jul 26, 2013 at 10:04 PM, Stephan Sokolow > <gma...@sp...> wrote: >> It'd make sense for it to be more advanced. As I understand it, it's a >> simplified frontend to JIRA and I'd be very surprised if they pared >> something as featureful as JIRA down as far as GitHub Issues. >> >> I don't really mind BitBucket too much. It's nicer and more featureful >> than Google Code, less annoying than SourceForge, and the main ways it >> falls short of GitHub are things that don't apply here. >> >> For example, LXDE already has its own hosting, so their lack of a GitHub >> Pages equivalent (last I checked) isn't an issue. >> >> They do apply a spam filter to even the logged-in bug tracker posts >> (Akismet, I think) and that's bitten me once or twice, but it's probably >> not a huge issue, and their assumption that e-mail bug replies will come >> from a From: address known to their system is a weakness, but I never >> trust bug replies without a preview so I don't use that anyway. >> >> Having the option of logging in using OpenID or using an existing GitHub >> account as an OAuth provider to sign in is also a plus. >> >> On 13-07-26 09:30 AM, PICCORO McKAY Lenz wrote: >>> *what about bitbucket *? the web interface are more light and do not >>> have too many js process in background... issue tracker seems more >>> avanced rather than github... >>> >>> On Fri, Jul 26, 2013 at 7:14 AM, Andrej N. Gritsenko <an...@re... >>> <mailto:an...@re...>> wrote: >>> >>> What bothers me in that article is the sentence "Currently >>> github is >>> more favored." We all discussed that github is a temporary solution... I >>> hate github really, it is very inconvenient in some aspects and their >>> "issue tracker" is poor at the best. I hardly have any desire to work >>> with that "issue tracker", the same way as some developers ignore the SF >>> one. >>> >>> i really hate github and sf due the web interface, use a lot of js that >>> make my browser consumes lot of memory.. and some thing do not work due >>> "u need to upgrade u'r browser" rule... >>> >>> Well, if you go back and want github not as temporary solution >>> but as >>> main host for the project, I will not go agaisnt you but I will be >>> set to >>> find a solution for code that I work with. For GIT web interface I >>> have a >>> solution - I just install the GitWeb on one of my websites and will use >>> >>> as i said.. and then this seems a good solution if plans are use github.. >>> >>> it, pushing code time to time into your loved github, but github's >>> "issue >>> tracker" will never have my love so I will rarely come there and answer >>> any questions, that will be all your job. I'm sorry. >>> >>> i agree >>> > > Bitbucket has one waek point. > It's a paid service. Free users have many limitations. > If we're going to use it, then we probably need some sponsor to pay for it. > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > |
From: <chr...@su...> - 2013-07-27 09:20:56
|
fredag den 26. juli 2013 skrev PCMan : > Hello, > Hi > Sorry to bother you guys with the same topic again. > It's really time-consuming to do the communication stuff, but it's > inevitable. > It's better to have some consensus before really starting coding. > While the razor guys are doing their best pushing razor-qt 0.6 as > planned, I'd like to start preparing for the merge earlier. > > I wrote another wiki page, which is a draft for the merge and hope we > can coordinate better. > It also documented what we already have (but the list is not complete). > > http://wiki.lxde.org/en/Merge_LXDE-Qt_and_Razor-Qt > > Nothing is settled done yet. It's only a draft. > Some are just my own opinions and I wrote them down for ease of discussion. > Anything can be changed if anyone has different opinions. > Feel free to add different opinions either on the wiki page or discuss > in the ML. > > Previously we discussed about using single monolithic repo or > splitting razor-qt into smaller repos. > Seems that there are no objections about splitting it into smaller pieces. > I'd like to know if it's the right time to do it, or we need to wait > for razor-qt 0.6 release? > > We also need to know who is interested in working on which part so we > won't duplicate the work. > I'll work on: * lightdm-greeter. I have no plans atm. to add new features to razor-lightdm-greeter, so it's mainly a matter of putting it into lxde-qt. So should it be a module of it's own (a bit small for a module perhaps) or where could it be placed? One problem, though, is that it shows razor's pizza-slicer icon. We'll need a new icon before we make an lxde-qt release :-). * razor-autosuspend I'd like to rewrite razor-autosuspend into two applications: One monitoring the lid, and one monitoring the battery (follow the principle of 'do one thing and do it well'). * razor-screen-locker. Alec Moskvin started this, but I don't think he'll be working further on it. He wrote a todo-list ( https://groups.google.com/forum/#!topic/razor-qt/1SXteGRKB7I), and I'll work from that. With razor-autosuspend split in two together with razor-screen-locker we'll have 3 power-management applications: - a battery-monitor - a laptop-lid-monitor - a user-idleness-monitor. This covers at least what I personally need from my desktop * razor-config-file-associations. Again - I have no plans for new features, so it is mainly a question of how it should be placed in the lxde-qt repositories. There may be some issues regarding xdg-spec-compliance, but this should be dealt with in the qtxdg libraries. Alexander has written most of that, but I'll help out if I can. br. Chr. Regarding to the lxde side: > I'll work on the file manager part and try to see if I can make a > obconf qt port (openbox configuration tool). > About the panel, I'm willing to work on razor-panel instead of my own > poor lxpanel-qt. After I finish my file manager stuff, I'll see if > there's anything I can help for razor-panel. > Andriy is working on libfm and will make a new release soon. > Julien is working on lxsession now. > BTW, Julien, would you please document the dbus interface lxsession > currently provides in the wiki? > > Since lxsession is currently more feature-rich than razorqt-session > and it's a non-GUI program, I'd like to know if we can use lxsession > and make it adopt current razorqt-session features, including the > config dialogs. > Or if there're objections, at least we can make lxsession and > razorqt-session interchangeable first. > Comments are really wanted. > > Thank you all. > > -- > -- > You received this message because you are subscribed to the Google > Groups "Razor-qt" group. > For more options, visit this group at > http://groups.google.com/group/razor-qt?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Razor-qt" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to raz...@go.... > For more options, visit https://groups.google.com/groups/opt_out. > > > |
From: <chr...@su...> - 2013-07-27 09:31:08
|
lørdag den 27. juli 2013 skrev chr...@su... : > > > fredag den 26. juli 2013 skrev PCMan : > >> Hello, >> > > Hi > > >> Sorry to bother you guys with the same topic again. >> It's really time-consuming to do the communication stuff, but it's >> inevitable. >> It's better to have some consensus before really starting coding. >> While the razor guys are doing their best pushing razor-qt 0.6 as >> planned, I'd like to start preparing for the merge earlier. >> >> I wrote another wiki page, which is a draft for the merge and hope we >> can coordinate better. >> It also documented what we already have (but the list is not complete). >> >> http://wiki.lxde.org/en/Merge_LXDE-Qt_and_Razor-Qt >> >> Nothing is settled done yet. It's only a draft. >> Some are just my own opinions and I wrote them down for ease of >> discussion. >> Anything can be changed if anyone has different opinions. >> Feel free to add different opinions either on the wiki page or discuss >> in the ML. >> >> Previously we discussed about using single monolithic repo or >> splitting razor-qt into smaller repos. >> Seems that there are no objections about splitting it into smaller pieces. >> I'd like to know if it's the right time to do it, or we need to wait >> for razor-qt 0.6 release? >> >> We also need to know who is interested in working on which part so we >> won't duplicate the work. >> > > I'll work on: > > * lightdm-greeter. I have no plans atm. to add new features to > razor-lightdm-greeter, so it's mainly a matter of putting it into lxde-qt. > So should it be a module of it's own (a bit small for a module perhaps) or > where could it be placed? > One problem, though, is that it shows razor's pizza-slicer icon. We'll > need a new icon before we make an lxde-qt release :-). > > * razor-autosuspend I'd like to rewrite razor-autosuspend into two > applications: One monitoring the lid, and one monitoring the battery > (follow the principle of 'do one thing and do it well'). > > * razor-screen-locker. Alec Moskvin started this, but I don't think he'll > be working further on it. He wrote a todo-list ( > https://groups.google.com/forum/#!topic/razor-qt/1SXteGRKB7I), and I'll > work from that. > > > With razor-autosuspend split in two together with razor-screen-locker > we'll have 3 power-management applications: > > - a battery-monitor > - a laptop-lid-monitor > - a user-idleness-monitor. > > Hmm. Maybe it was a bit unclear why I consider razor-screen-locker part of power-management: In addition to locking the screen it should be able to dim screen/suspend/hibernate/shut down. br. Chr. > This covers at least what I personally need from my desktop > > * razor-config-file-associations. Again - I have no plans for new > features, so it is mainly a question of how it should be placed in the > lxde-qt repositories. There may be some issues regarding > xdg-spec-compliance, but this should be dealt with in the qtxdg libraries. > Alexander has written most of that, but I'll help out if I can. > > br. Chr. > > > > Regarding to the lxde side: >> I'll work on the file manager part and try to see if I can make a >> obconf qt port (openbox configuration tool). >> About the panel, I'm willing to work on razor-panel instead of my own >> poor lxpanel-qt. After I finish my file manager stuff, I'll see if >> there's anything I can help for razor-panel. >> Andriy is working on libfm and will make a new release soon. >> Julien is working on lxsession now. >> BTW, Julien, would you please document the dbus interface lxsession >> currently provides in the wiki? >> >> Since lxsession is currently more feature-rich than razorqt-session >> and it's a non-GUI program, I'd like to know if we can use lxsession >> and make it adopt current razorqt-session features, including the >> config dialogs. >> Or if there're objections, at least we can make lxsession and >> razorqt-session interchangeable first. >> Comments are really wanted. >> >> Thank you all. >> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Razor-qt" group. >> For more options, visit this group at >> http://groups.google.com/group/razor-qt?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Razor-qt" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to raz...@go.... >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> |