Hi.
I'm not sure if I understood you so I have some questions.
1. Now everything will be in LXDE-Qt repo ([1]https://github.com/lxde)?
Maybe better idea is create new repo and fork everything what we want
to use?
2. If someone decalre to work on something thats mean only he/she will
be working on this piece of code? Or it just mean he/she is reponsible
for it (decide what should be done for the next version, review patches
from community and accept it etc)?
3. Project will be on GithuB, BitBucket, SF?
4. Project name is LXDE-Qt, Razor-qt, or there will be new name?
And my opinions.
1. I'm really happy for this team merging. I really enjoy Razor-qt and
I'm sure I will use LXDE-Qt. So +1 from me ;)
2. I think LXDE-Qt should be splitted into separate projects (panel,
session, desktop etc). Of course common stuff will go to the project
"common" or smth like that.
Best regards.
On Sat, Jul 27, 2013, at 11:31 AM, [2]christ...@surlykke.dk wrote:
lørdag den 27. juli 2013 skrev [3]christ...@surlykke.dk :
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).
[4]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
([5]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
[6]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 razor-qt+unsubscr...@googlegroups.com.
For more options, visit [7]https://groups.google.com/groups/opt_out.
--
--
You received this message because you are subscribed to the Google
Groups "Razor-qt" group.
For more options, visit this group at
[8]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 razor-qt+unsubscr...@googlegroups.com.
For more options, visit [9]https://groups.google.com/groups/opt_out.
--
Maciej Płaza
References
1. https://github.com/lxde
2. mailto:christ...@surlykke.dk
3. mailto:christ...@surlykke.dk
4. http://wiki.lxde.org/en/Merge_LXDE-Qt_and_Razor-Qt
5. https://groups.google.com/forum/#!topic/razor-qt/1SXteGRKB7I
6. http://groups.google.com/group/razor-qt?hl=en
7. https://groups.google.com/groups/opt_out
8. http://groups.google.com/group/razor-qt?hl=en
9. https://groups.google.com/groups/opt_out
------------------------------------------------------------------------------
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
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
