Sandip Dev | 1 Sep 12:52 2009
Picon

Come join me at SFD at NIT Surat on Open Source University Meetup

Open Source University Meetup
Sandip Dev has invited you to the event 'SFD at NIT Surat' on Open Source University Meetup!
 
Hi,
ACM SVNIT Student Chapter is celebrating Software Freedom Day on Sept 19th and the celebrations would continue up to Sept 26. Do register for the event at Open Source University Meetup :)

Time: September 19, 2009 to September 26, 2009
Location: Computer Engineering Department, SVNIT
Organized By: Sandip Dev

Event Description:
SFD celebrations at NIT Surat will begin on Sept 19th and will continue upto Sept 26. Lots of events are planned including those on Sun technologies. To keep updated please visit www.svnit.edu.in/acm . The ACM Student Chapter of SVNIT will spearhead the events.


See more details and RSVP on Open Source University Meetup:
http://osum.sun.com/events/event/show?id=2181626%3AEvent%3A1070337&xgi=e7DwTbn
About Open Source University Meetup
107233 members
735 videos
8634 discussions
2001 blog posts
 
To control which emails you receive on Open Source University Meetup, click here
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Owen Taylor | 1 Sep 22:14 2009
Picon

Searching for patches in bugzilla

Finding patches in your component that haven't been reviewed is a pretty
common operation. Our previous ways of doing it (emblems, links from
browse.cgi) aren't working at the moment, so I thought I'd mention here
how to do it with the boolean charts feature, since I had trouble
figuring it out.

A screenshot is attached that demonstrates.

Note that it's important that this is all in one boolean chart - because
it's in one boolean chart, all the checks that are anded together have
to match on the *same* attachment.

Since you don't want to have to do this frequently, you should set up
the search once for your module, than save it as a named query.

- Owen

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Kjartan Maraas | 1 Sep 22:34 2009
Picon

Re: Searching for patches in bugzilla

ti., 01.09.2009 kl. 16.14 -0400, skrev Owen Taylor:
> Finding patches in your component that haven't been reviewed is a pretty
> common operation. Our previous ways of doing it (emblems, links from
> browse.cgi) aren't working at the moment, so I thought I'd mention here
> how to do it with the boolean charts feature, since I had trouble
> figuring it out.
> 
> A screenshot is attached that demonstrates.
> 
> Note that it's important that this is all in one boolean chart - because
> it's in one boolean chart, all the checks that are anded together have
> to match on the *same* attachment.
> 
> Since you don't want to have to do this frequently, you should set up
> the search once for your module, than save it as a named query.
> 
Note that the right patch status would be accepted-commit_now and
accepted-commit_after_freeze with underscores instead of hyphens.

Other options are: reviewed, needs-work, rejected, commited.

Cheers
Kjartan
Ray Strode | 1 Sep 23:39 2009
Picon

Re: Searching for patches in bugzilla

Hi,

On Tue, Sep 1, 2009 at 4:34 PM, Kjartan Maraas<kmaraas <at> broadpark.no> wrote:
> ti., 01.09.2009 kl. 16.14 -0400, skrev Owen Taylor:
>> Finding patches in your component that haven't been reviewed is a pretty
>> common operation. Our previous ways of doing it (emblems, links from
>> browse.cgi) aren't working at the moment, so I thought I'd mention here
>> how to do it with the boolean charts feature, since I had trouble
>> figuring it out.
>>
>> A screenshot is attached that demonstrates.
>>
>> Note that it's important that this is all in one boolean chart - because
>> it's in one boolean chart, all the checks that are anded together have
>> to match on the *same* attachment.
>>
>> Since you don't want to have to do this frequently, you should set up
>> the search once for your module, than save it as a named query.
>>
> Note that the right patch status would be accepted-commit_now and
> accepted-commit_after_freeze with underscores instead of hyphens.
I added a

and CC is %user%

to this query and saved it as a global search:

Bugs I watch with patches

Which I think people should be able to access by going to

http://bugzilla.gnome.org/userprefs.cgi?tab=saved-searches

and checking it from the bottom list

--Ray
Pierre Slamich | 3 Sep 00:40 2009
Picon

GlobalMenu Application for inclusion as a GNOME module

Dear GNOME maintainers,

This is a proposal on behalf of the GlobalMenu developers for its inclusion either in gnome-applets or as a dependency of GNOME.

GlobalMenu is an applet that lets the user have its application menus displayed in the Panel rather than in the windows. For those who haven't heard about it, think of GNUStep or MacOS as an example. Or you can look at a screenshot to get an idea http://code.google.com/p/gnome2-globalmenu



- Target: proposed for the desktop module set
- Dependencies: No new dependencies are introduced for either compiling the released tarball or the runtime. An up-to-date vala compiler for the developers.
- Resource usage: currently no NOME infrastructure are allocated for the project. Google Code is the main hosting service and Launchpad is used for Ubuntu packaging and translations. We have sent a mail to apply for GNOME resources.
- Adoption in Distributions: none so far (Ubuntu Netbook Remix has shown some interest)



- GNOME-ness & community: The project uses VALA as the main programming language. Various bugs in VALA were discovered and fixed by the Global Menu developers. For the moment the team doesn't strongly need to cooperate with the internationalization, user documentation, accessibility, usability, bugsquad teams (and etc) of the community. The team is always open to such cooperation.

- License : GlobalMenu is currently licensed under the GPLv2+ and LGPLv2+. The documentation and the majority of the code have all been written by team members; therefore the project can be easily re-licensed to meet the GNOME requirements.

- We have a pool of developers, committed doc writers, bug hunters and translators which is an asset to keep deadlines, and to bring innovation, along with quality assurance. We have a good track record, as can be seen throughout our issue tracker and our Ubuntuforums thread. We strive to keep aware of all the evolutions going around, we successfully coordinated with KDE for the spread of the GlobalMenu spec beyond our initial GNOME focus.

- Willingness and ability to follow release rules and release schedule and progress on a regular basis: We have an Italian dev, but we also have a German dev and a Chinese dev. Overall, we have thus time-conscious people ;-)

- Improving overall desktop usability: The document-centric functionalities of Global Menu are available on GNUStep and MacOS, but most importantly we think that it's a very nice addition to the already strong GTK stack that will, playing along GNOME Shell, enable application developers to build upon it. Moreover, it's implemented in a better way than the other globalmenu implementations, listening to user feedback and building upon Gnome's unique features. We have relatively wide compatibility, and we believe adoption in Gnome 2.30/3.0 would enable further adoption and standardisation on the developer side, pushing ISV to provide native GTK interfaces for at least the menus (Firefox, OpenOffice, Java to name a few). This will both push GNOME's interface forward, and push the GTK-toolkit forward.

- Developer attitude: We like to engage with upstream (GNOME for the moment :-), possibly the Freedesktop's project afterwards for standardization) and downstream, as well as our user base. We're very open and our forum thread and our bug tracker testifies that. We have an open development process and we prefer daily commits to large code drops. We engaged with GNOME, we also engaged with XFCE and KDE. We're nice and cool people (really :-)

- GNOME-ness: We use GTK2 and other GNOME2 technologies (VALA, all the standard GNOME guidelines and techniques) and we have a GNOME look and feel. We rewrote the software from ground to bottom to use the state of the art technologies. We of course don't use the obsolete stuff that GNOME 3 aims to get rid of.

- UI: We have no problem engaging with the UI team to make GlobalMenu even better UI-wise. We strive to keep in line with the GNOME look and feel, HIG compliance, a careful choice of default settings, and clean interface design.

- Accessibility: Though we haven't delved into the matter, we're also ready to engage should issues arise.

- Internationalization is already done in the GNOME-compliant fashion. All text is i18n-ized and the app is localized (RTL).

- Use of GNOME resources: While we don't currently use them, we'll be happy to switch should our inclusion be accepted, and we have actually already applied to get GlobalMenu on GNOME's infrastructure.

- Documentation: Documentation already exists in the project wiki, and our code is clear and clean. We're willing either to help the existing docs team on incorporating our current document or to directly join them in this work. We're anyway motivated to make useful documentation available. Nevertheless we will strive to make GlobalMenu as simple as possible while increasing its power. We'll contact soon the GNOME Documentation Team to organize about the matter.

- Relation with GNOME 3.0: As proposed in GNOME 3.0, the Shell features a menu item which provides the access to the application's actions. The idea is good, however most current applications in GNOME do not support this feature. Neither does the GTK toolkit provide the necessary facilities for it. While we need to systematically invent it in GNOME 3.0 (eg, by extending GtkUIBuilder), some kind of legacy support should also be provided. This is where Global Menu becomes relevant to GNOME 3.0. Global Menu already has the code to extract the main menu bar from the applications. Once the global menu plugin for GTK is enabled (and it can be selectively enabled), each GtkWindow instance will carry a special property containing an introspection of its menu bar, and the sub menus. This information can be used to reconstruct a menu in the Shell's application menu item. Global Menu also provides a protocol to sync the selection and activation of menu items.




Thanks a lot for bearing with that long and overly detailed proposal. I look forward to your reviews, comments, suggestions, bashings, etc :-)

Yu and Pierre, on behalf of the whole GlobalMenu team
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Sandy Armstrong | 3 Sep 01:17 2009
Picon

Re: GlobalMenu Application for inclusion as a GNOME module

On Wed, Sep 2, 2009 at 3:40 PM, Pierre Slamich<pierre.slamich <at> gmail.com> wrote:
> Dear GNOME maintainers,
>
> This is a proposal on behalf of the GlobalMenu developers for its inclusion
> either in gnome-applets or as a dependency of GNOME.
>
> GlobalMenu is an applet that lets the user have its application menus
> displayed in the Panel rather than in the windows. For those who haven't
> heard about it, think of GNUStep or MacOS as an example. Or you can look at
> a screenshot to get an idea http://code.google.com/p/gnome2-globalmenu

Assuming gnome-panel (and therefore panel applets) go away in GNOME
2.30, do you have a plan for integrating GlobalMenu in gnome-shell?

Sandy
John Stowers | 3 Sep 12:44 2009
Picon

Re: GlobalMenu Application for inclusion as a GNOME module

On Thu, 2009-09-03 at 00:40 +0200, Pierre Slamich wrote:
> Dear GNOME maintainers,
> 
> This is a proposal on behalf of the GlobalMenu developers for its
> inclusion either in gnome-applets or as a dependency of GNOME.

+1 from me, I use this daily, and it works wonderfully.

While some might argue that the GTK_MODULES implementation is hacky it
works well in practice.

John
Patryk Zawadzki | 3 Sep 12:58 2009

Re: GlobalMenu Application for inclusion as a GNOME module

On Thu, Sep 3, 2009 at 12:44 PM, John
Stowers<john.stowers.lists <at> gmail.com> wrote:
> On Thu, 2009-09-03 at 00:40 +0200, Pierre Slamich wrote:
>> Dear GNOME maintainers,
>>
>> This is a proposal on behalf of the GlobalMenu developers for its
>> inclusion either in gnome-applets or as a dependency of GNOME.
> +1 from me, I use this daily, and it works wonderfully.
>
> While some might argue that the GTK_MODULES implementation is hacky it
> works well in practice.

Unless you ever want to use an MPX-enabled X server of course ;)

--

-- 
Patryk Zawadzki
Ted Gould | 3 Sep 15:39 2009

Re: GlobalMenu Application for inclusion as a GNOME module

On Thu, 2009-09-03 at 12:58 +0200, Patryk Zawadzki wrote:
> On Thu, Sep 3, 2009 at 12:44 PM, John
> Stowers<john.stowers.lists <at> gmail.com> wrote:
> > On Thu, 2009-09-03 at 00:40 +0200, Pierre Slamich wrote:
> >> Dear GNOME maintainers,
> >>
> >> This is a proposal on behalf of the GlobalMenu developers for its
> >> inclusion either in gnome-applets or as a dependency of GNOME.
> > +1 from me, I use this daily, and it works wonderfully.
> >
> > While some might argue that the GTK_MODULES implementation is hacky it
> > works well in practice.
> 
> Unless you ever want to use an MPX-enabled X server of course ;)

I don't understand.  Why is MPX incompatible with Global Menu?

		--Ted

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Colin Walters | 3 Sep 15:44 2009

Re: GlobalMenu Application for inclusion as a GNOME module

On Wed, Sep 2, 2009 at 7:17 PM, Sandy
Armstrong<sanfordarmstrong <at> gmail.com> wrote:
>
> Assuming gnome-panel (and therefore panel applets) go away in GNOME
> 2.30, do you have a plan for integrating GlobalMenu in gnome-shell?

The design for 3 is currently that application-global actions go in
the application menu area, while document or window-specific ones
remain in the window.

Gmane