Re: Giving up maintainership of Dictionary and 2048
Hi, I'm sorry to hear that Pranav can't take the maintainership of gnome-dictionary. So I'm stepping in. As Pranav, I have no previously experience patching Dictionary, but I've been involved in some other GNOME projects and I think this is a great opportunity to learn and give back to the community. If you agree, I'd like to maintain gnome-dictionary from now on. On Wed, Sep 16, 2015 at 8:10 PM, Pranav Kant wrote: > I am sorry for first jumping in, and then not following this up. > > I got a job soon after sending this email, and hence never got enough time > to look into it as planned. > > On Wed, Aug 19, 2015 at 7:08 PM, Pranav Kant wrote: >> >> Hi, >> >> On Wed, Aug 19, 2015 at 4:17 PM, Emmanuele Bassi wrote: >> > Hell Juan; >> > >> > first of all, I'd like to thank you for the terrific job you did as >> > the Dictionary maintainer. You're a hero, and your work has been very >> > much appreciated. >> > >> > On 19 August 2015 at 09:58, Juan Rafael García Blanco >> > wrote: >> > >> >> Regarding Dictionary, we recently started updating its UI to adapt it >> >> to the >> >> upstream Gnome look and feel. I wish I had finished it for the 3.18 >> >> release, >> >> but unfortunately I have not :( Of course, please feel free to ask me >> >> about >> >> any recent changes on it. >> > >> > I'm sure the current UI, while not perfect, is already a vast >> > improvement over the old, 2.x style UI that I wrote all those years >> > ago. :-) >> > >> >> I just want to say it has been a really great experience, I'm very >> >> thankful >> >> to all of you; without the help of the Gnome community I would have not >> >> even >> >> made the first release. So thank you. >> > >> > Again, thanks to you for your hard work. >> > >> > If somebody wants to pick up the Dictionary, I'd also be happy to >> > mentor new developers. >> > >> Hi, >> >> I would like to take this opportunity. I would love to maintain and >> work on this module. >> >> Though, I do not have any experience/patches in gnome-dictionary as of >> now, but looking at the codebase, >> I think it should not be too hard for me to adapt, and work on this. >> >> Besides that, I am also excited to work under your mentorship. >> >> Thanks. >> >> -- >> Regards, >> Pranav Kant >> http://pranavk.me > > > > > -- > Regards, > Pranav Kant > http://pranavk.me > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Online Service API keys
On Sat, Oct 10, 2015 at 5:26 PM, Tomasz Torcz wrote: > On Fri, Oct 09, 2015 at 02:12:06PM -0500, Michael Catanzaro wrote: >> On Fri, 2015-10-09 at 17:41 +0300, Alberto Mardegan wrote: >> > Unless Yorba manifests some interest in getting the Facebook >> > integration >> > fixed in Shotwell, would GNOME be willing to takeover the project, >> > and >> > consequently the associated Facebook application key? >> >> To be clear, Shotwell is a GNOME project since it was recently moved to >> git.gnome.org. But it's clearly not being developed anymore, > > Slightly offtopic: we had F-Spot but the development ceased. Then > we had Shotwell which seems dead now. Is GNOME left without easy, > tagging photo manager? What about Photos (gnome-photos)?? > > -- > Tomasz .. oo o. oo o. .o .o o. o. oo o. .. > Torcz.. .o .o .o .o oo oo .o .. .. oo oo > o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME Music needs you!
Hello everyone! Music is one of those core applications that we all love. It follows a design-oriented approach, and it's written on Python. Music has been a little abandoned since the last release, and it still lacks some important features. Therefore, I hereby invite you all, experienced and newcomers, to help us keep this app alive. Reach us out at #gnome-music on irc if you are willing to help! https://wiki.gnome.org/Apps/Music ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Dictionary release 3.19.92
Hi, No problem. I am going to do it. Regards, Felipe Borges. On Sun, Mar 20, 2016 at 12:08 PM, Juan Rafael García Blanco wrote: > Hi, > > Unfortunately, I’ll not be able to make the next big one either :( If someone > could take this responsibility for now, that would be great. > > Thank you. Regards, > Juan. > >> On 13 Mar 2016, at 16:02, Michael Catanzaro wrote: >> >> On Sun, 2016-03-13 at 10:12 +0100, Juan Rafael García Blanco wrote: >>> Hi all, >>> >>> Unfortunately, I will not be able to make the 3.19.92 release of >>> Dictionary >>> (gnome-dictionary). Could anyone please do this for me? Only >>> translations >>> have been updated. >> >> If only translations have been updated then I think it's fine to wait >> until 3.20.0. > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-settings-daemon/gnome-control-center under new ownership
On Thu, May 18, 2017 at 4:49 PM, Bastien Nocera wrote: > Hey, > > At GUADEC 2010, Matthias asked Richard Hughes and I to help with gnome- > control-center's port to GTK+ 3.x and update all the panels to the new > control-center shell that Jon McCann had been polishing. > > Skip forward 7 years later, and I'm mostly doing patch reviews for > features and redesigns done by others, along with being the person that > rejects adding new options. Thank you for your service. Apart from keeping our code base sane you have mentored many of us with your reviews and standard of quality. > Rui will be taking over handling of day-to-day operations for gnome- > control-center and gnome-settings-daemon. I'll still be around to > handle bugs in my own area of expertise (such as the Bluetooth panel or > the fingerprint integration). We are in very good hands as well! > > Cheers > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to deploy GitLab on gnome.org
On Tue, May 23, 2017 at 11:00 AM, Milan Crha wrote: > On Thu, 2017-05-18 at 15:12 -0500, mcatanz...@gnome.org wrote: >> I think we should remove this extension immediately. > > Hi, > that sounds quite radical, does it not? > > Removing everything what has bugs, instead of fixing them, what would > you ship to your users? > >> It provides limited value, since you almost always want to skip >> through the pretty little trace to see the full backtrace anyway. > > Different people, different usages. What you do not use maybe others > do. I see many regressions in the recent changes in GNOME bugzilla > which simply break my workflow with it, built and fine-tuned during > many years of using it, but nobody cares. They know better what I > should do and how, it seems. > >> And this confusing bug is very serious. > > Hmm, did you hit that bug yourself? I did not. I see it's filled since > 2015, with 18 CC'ed users. That's not a low number, but there had been > filled thousands of backtraces during that time, with no problem so far > (I believe so at least, I do not have exact numbers, thus if anyone can > correct my expectations, then I'm all fine). > Bye, > Milan > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list +1: I am supportive of the initiative. After catching up with the discussion, my personal pros and cons are: Pros: - reviewing patches is significantly clearer in gitlab - code browsing is better than cgit - gitlab snippets introduce a bit more flexibility than pastebin - easy to publish new repositories with toy/new projects Cons: - not a big fan of the merge-request workflow - we will have a bunch of useless forks across the users' accounts In terms of issue/bug tracking, I am more concern about the migration itself. I would initially use gitlab to replace cgit and pastebin, and keep bugzilla as the bug tracker for a little while (not introducing new components/modules on bugzilla anymore, pointing at gitlab). One common thing I do with git-bz is interactively applying patches. Is there a clear 101 workflow for this kind of review with gitlab? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to deploy GitLab on gnome.org
On Tue, May 23, 2017 at 2:13 PM, Adrian Perez de Castro wrote: > Hi there, > > No strong opinion here about GitLab, just a comment below... > > On Tue, 23 May 2017 11:21:25 +0200, Felipe Borges > wrote: > >> [...] >> >> Cons: >> - not a big fan of the merge-request workflow >> - we will have a bunch of useless forks across the users' accounts > > I have seen this concern pop several times in this thread. Does GitLab > strictly require that a merge request is always started from a fork? > > At least with GitHub and Gogs [1] it's possible to create merge requests from > a branch *in the same repository* (I use branches named “/” > now and then). If everybody who is a maintainer is going to have push access > in the GNOME GitLab instance, they can just push their branch to repository > and create the merge request from there — without needing to fork the > repository into their user space. Sure, but this creates a distinction between maintainers and other contributors, as I think Bastien mentioned before. > > Cheers, > > -- > 💻 Adrián “2¢” Pérez > --- > [1] > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Matrix as a replacement for Telepathy
On Fri, Aug 25, 2017 at 12:15 AM, Alejandro HC wrote: > A comment as a user. Since Empathy ceased to be maintained, there has been > little concern for the communication system that is available in gnome > focused to end user (gnome-polari is targeted to IRC which is mostly used by > developer communities). > > Matrix is great, but I feel it points to the same, so why not support GNU > Ring in GNOME ... Ring is a project that aims to be a free replacement for > Skype, in addition already has a good integration in gnome and it's easy to > use, offering its own communication protocol it offers support for SIP. Telepathy was designed as a framework which could have various "Connection Managers" (in the telepathy terminology). A Connection Manager is responsible of doing the actual communication with a given server through a given protocol. Telepathy has connection managers for XMPP, SIP, IRC, etc... see [0]. For instance, Polari uses Telepathy for the IRC protocol. All in all, if desirable, Matrix and GNU Ring could be connection managers in Telepathy instead of standalone bits. Specific clients could be created backed by Telepathy, e.g. no need to rely on Empathy. [0] https://telepathy.freedesktop.org/components/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Include GNOME Usage in the future releases
Hi everyone, We have been discussing for quite some time the inclusion of GNOME Usage in the GNOME release, initially as a "demo". The project has been evolving quite fast and it is expected to have an Outreachy student working on it as well. This way, I would like to know whether there are any objections regarding the $subject. Ideally we would ship it as a demo in GNOME 3.28, but it would be a good test to include it in the 3.27.x series too. Thanks, Felipe. https://wiki.gnome.org/Apps/Usage https://gitlab.gnome.org/GNOME/gnome-usage ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Include GNOME Usage in the future releases
Hi, Thanks for answering! On Mon, Oct 16, 2017 at 5:19 PM, Adrien Plazas wrote: > Hi Felipe, > > I just gave a quick look at the application and it looks great! I could > see myself using it over baobab or System Monitor, despite how much I like > these applications. ☺ > > During my quick test I encountered many crashes. The application would > benefit from broader testing and including it as a demo version in a GNOME > release would clearly bring, but having it part of a GNOME release means > branding it to the end users. I would suggest to first get the app in a > more stable test by promoting its usage inside the community before even > discussing whether it should be part of a GNOME release or not, at least > for the next month. > Yes, that's a chicken-egg dilemma. Usage hasn't been tested by many users so far and we the main motivation of this email was to promote it to a broader audience. > Cheers, > Adrien Plazas > > Le lun. 16 oct. 2017 à 16:27, Felipe Borges a > écrit : > > Hi everyone, We have been discussing for quite some time the inclusion of > GNOME Usage in the GNOME release, initially as a "demo". The project has > been evolving quite fast and it is expected to have an Outreachy student > working on it as well. This way, I would like to know whether there are any > objections regarding the $subject. Ideally we would ship it as a demo in > GNOME 3.28, but it would be a good test to include it in the 3.27.x series > too. Thanks, Felipe. https://wiki.gnome.org/Apps/Usage > https://gitlab.gnome.org/GNOME/gnome-usage > ___ > desktop-devel-list mailing list desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > > I just included gnome-usage into the gnome-apps-3.28 JHbuild moduleset, so if you want to try it you can also use: jhbuild build gnome-usage ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Include GNOME Usage in the future releases
On Wed, Oct 18, 2017 at 11:57 AM, Sébastien Wilmet wrote: > On Mon, Oct 16, 2017 at 05:47:29PM +0200, Felipe Borges wrote: >> On Mon, Oct 16, 2017 at 5:19 PM, Adrien Plazas >> wrote: >> > During my quick test I encountered many crashes. The application would >> > benefit from broader testing and including it as a demo version in a GNOME >> > release would clearly bring, but having it part of a GNOME release means >> > branding it to the end users. I would suggest to first get the app in a >> > more stable test by promoting its usage inside the community before even >> > discussing whether it should be part of a GNOME release or not, at least >> > for the next month. >> >> Yes, that's a chicken-egg dilemma. Usage hasn't been tested by many users >> so far and we the main motivation of this email was to promote it to a >> broader audience. > > Is it really a chicken-egg dilemma? Are the crashes and bugs specific to > some hardware or underlying software configuration? Or are the bugs > always reproducible by the maintainer? If it's the latter, I don't see > why it is a chicken-egg dilemma, you have everything in hand to write > (mostly) stable software from day 1. > > -- > Sébastien > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list Ok, so it is a no-go. Thanks everybody. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: [GSoC] Urgent action required: Call for ideas
On Fri, Jan 26, 2018 at 10:57 AM, Adrien Plazas via desktop-devel-list wrote: > Do you need them by today (Friday 26th) or tomorrow (Saturday 27th)? Tomorrow, January 27th. > Cheers, Adrien Plazas > > Le ven. 26 janv. 2018 à 9:55, Carlos Soriano a écrit : > > Dear GNOME hackers, > > It's this time of the year again, GSoC is here! > > It's time for mentors to add their project ideas. Unfortunately this year we > felt a bit behind schedule, and we need to have this done by this Saturday > 26th to give us admins time to review them. So please add them ASAP to our > wiki page [0]. > > The ideas can be drafts, it's more important the intention on mentorship and > number of students you would like to mentor. > > Also, allow me to welcome Felipe Borges as part of the team this year! > Thanks for joining Felipe! > > If you have any questions, please don't hesitate to send us an email to > soc-adm...@gnome.org or contact one of us on IRC. > > Best, > GNOME GSoC Admins > > [0] https://wiki.gnome.org/Outreach/SummerOfCode/2018/Ideas > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Github's pull requests warning still point to Bugzilla
Hi, On Fri, 5 Oct 2018, 22:31 Jonathan Demeyer via desktop-devel-list, < desktop-devel-list@gnome.org> wrote: > Hello, > > GNOME sets a cronjob that close all the pull requests for each repository > on Github (because it's a mirrored repo). The closure message looks like > this: > > """ > Thank you for contributing to $project_name! > > $project_name uses Bugzilla for code review. > > If you have never contributed to GNOME before make sure you have read the > getting started documentation:http://www.gnome.org/get-involved > > Otherwise please > visithttps://wiki.gnome.org/Newcomers/CodeContributionWorkflow > and follow the instructions there to upload your change to Bugzilla. > """ > > Ref: > https://mail.gnome.org/archives/desktop-devel-list/2016-November/msg00043.html > > GNOME has migrated from Bugzilla to Gitlab in May. The message should be > updated. > That's a good catch. Thank you. Here is my proposition : > > """ > Thank you for your effort contributing to $project_name! > > $project_name uses Gitlab for merge/pull requests. > We should link to our instance of gitlab (gitlab.gnome.org), to avoid confusion with gitlab.com Ideally we could link directly to https://gitlab.gnome.org/gnome/$project_name/issues but I'm not sure that there would be a match for 100% of our components mirrored in GitHub. > If you have never contributed to GNOME before make sure you have read the > getting started documentation: > http://www.gnome.org/get-involved > > Otherwise please visit > https://wiki.gnome.org/Newcomers/CodeContributionWorkflow > and follow the instructions there to upload your change to Gitlab. > """ > > Best regards, > > Jonathan > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: This Week in GNOME
Is there a way we (developers) could mark issues/MR to be picked up in the weekly report? On Thu, Dec 13, 2018 at 12:06 AM Niels De Graef via desktop-devel-list wrote: > > This looks good already, kind of reminds me KDE's 'This week in > Usability & Productivity', so good job! :-) > > One remark I have is that it might be interesting to see if a > maintainer (or heavily involved developer) of a project can give a > one-liner (or 2 liner) what the listed MRs are about. I'm afraid that > otherwise some MRs with very technical titles will get discarded by > the audience, while some MRs with a sensationalist or overexaggerating > title will lead to e.g. false expectations. > > Cheers, > nielsdg > On Wed, Dec 12, 2018 at 11:56 PM Sriram Ramkrishna wrote: > > > > We have a volunteer who is willing to do GNOME summaries every week. > > Here is what this week looks like. I'm looking for some feedback > > before we start using our social media outlets to start publishing it. > > > > https://bloerg.net/2018/12/07/gnome-weekly.html > > > > Please let me know your feedback. > > > > Cheers, > > sri > > > > ___ > > desktop-devel-list mailing list > > desktop-devel-list@gnome.org > > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal: Replace all references to master/slave in GNOME modules
On Thu, Apr 25, 2019 at 8:54 AM Daniel Mustieles García via desktop-devel-list wrote: > > Hi Michael, > > Please stop lying about changes in Django, Rust or Python branches' names... > they stil use «master» for the main branch. Here are the changes those > projects are discussing: > > Djando: db configuration. The comments in the issue you've mentioned are an > interesting reading... did you read them? > Rust: Like Djando, it's a change in source code, not in branch name > Python: Again... read above > > So no, your arguments are not valid and your change in the name of the branch > have caused problems in Damned Lies, automated scripts, etc. > > Please revert the change, it makes no sense to keep this discussion alive. . On Thu, Apr 25, 2019 at 10:21 AM Daniel Mustieles García via desktop-devel-list wrote: > > Do we need to remember you again the incovenients of your change? Damned Lies > is broken in Geary's module (cherry-pick doesn't work), developers and > contributors get confused if modules name their master branches to whatever > maintainers decide, you have broken GNOME's standard naming for development > branches, your arguments about Django, Rust, Linux Kernel are false, you've > done this change without asking the community, which is clearly against it... > do you want more reasons? Daniel, could you please be more careful about your wording here? This should be a civil conversation between colleagues and your choice of words can sound slightly aggressive to some people. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Bootable GNOME images available
Hi Tristan, thanks a lot for working on this. It is definitely going to help our development efforts both in CI and design. On Thu, Sep 19, 2019 at 11:39 AM Tristan Van Berkom via desktop-devel-list wrote: > > Hi all, > > It's my pleasure to announce that we are now producing bootable > images based on the very latest of GNOME modules as defined by the > gnome-build-meta[1] (which we also use to build the releases and > produce the GNOME flatpak runtime/sdk). > > At this time, the image is recreated every time the gitlab pipeline > runs, and can be downloaded from gitlab here[2]. In GNOME Boxes we have the "Download an OS" feature that makes it easier to obtain and install an OS. I would love to feature the GNOME images there. For that, could we hotlink directly to [2]? Will this link change? https://fedoramagazine.org/download-os-gnome-boxes/ Also, could we include spice guest tools in the image? This way Boxes could provide cool features such as "shared clipboard, automatic resolution, shared folders, sent files via drag and drop, and many more. My initial run of the image in Boxes showed that this adjustment will be necessary if we want people to run the VMs in Boxes. What is the best channel for us to discuss these things I mentioned above? Once again, thanks for your efforts, it is much appreciated! Cheers, Felipe. > > The image comes with a simple launcher script for qemu, and should boot > up to the gnome-initial-setup[3] tool automatically. > > > Next steps > ~~ > The current setup still leaves much to be desired, and we're hoping > others will pitch in and help improve our CI story. > > The next big task ahead of us is to boot the image in CI and perform > automated tests on it, most probably with openQA, you can follow that > issue here[4]. > > Of course there are many other things to accomplish: > > * Allow atomic upgrades with ostree, which requires some system > integration work and also requires that we publish the builds in a > publicly hosted ostree repository. > > * Currently we only build the image for 64bit intel, but we should > be able to boot for the 4 architectures we already support for the > GNOME Flatpak SDKs (i686, x86_64, armv7, aarch64). > > * Improve system integration in general, ensure input methods are > working, online accounts are integrated properly, keyring unlocks > with user login, etc. > > * Run installed tests as a part of the CI pipeline before wrapping > the image itself. > > * The list goes on and on :) > > > If you'd like to help out but need some pointers getting familiar with > the gnome-build-meta project, feel free to ask Javier or myself, and > other release team members should also be capable of pointing you in > the right direction. > > > Finally, thanks to everyone on the release team and also freedesktop-sdk > project contributors who have helped immensely to get us this far ! > > Cheers, > -Tristan > > > [1]: https://gitlab.gnome.org/GNOME/gnome-build-meta > [2]: > https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/artifacts/master/browse/image/?job=build-gnome-core-x86_64 > [3]: https://gitlab.gnome.org/GNOME/gnome-initial-setup > [4]: https://gitlab.gnome.org/GNOME/gnome-build-meta/issues/206 > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Want to join
Hi Ismael, welcome to GNOME! On Wed, Mar 11, 2020 at 10:46 AM Ismael Martinez via desktop-devel-list wrote: > > Hey there! > I'm Ismael Martinez from Chile. > I want to start contributing on open source project to get more > knowledge and learn from the biggest projects. > I'm an self-learner developer with a low level programming focus. > I think the best would be low complexity tasks in order to increase my > skills. Sounds great! We have a Newcomers guide that describes the process of fixing a bug in a GNOME application. https://wiki.gnome.org/Newcomers/ This should help you get started and also contains information about the next steps after you made your first contribution. Let us know if you have any issues while following the newcomers guide. Happy hacking! > > Kind regards! > Ismael Martinez C. > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Maintainership of Usage
Hi Adrien, On Sun, Jun 21, 2020 at 10:48 AM Adrien Plazas via desktop-devel-list wrote: > > Hi all, > > The Usage application seems to be unmaintained since 9 months at least, > while Felipe Borges resigned in due form a few months ago, the > remaining listed maintainer, Petr Štětka, isn't giving any sign of > life on our GitLab instance since at least a year. > > Do you mind if I take maintainership over so we can at the very least > fix the build and merge the MRs waiting since now 9 months? Sure! I'm glad you are interested in it. As I said in my commit message, I just happen to have too many things on my plate at the moment. I will be happy to help, but I can't at the moment dedicate time to develop the app. Thank you very much for stepping up! Cheers, Felipe Borges. > > Cheers, > Adrien Plazas > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Is libgd still a thing?
Evince bundles the whole libgd just so it can consume a two line cell renderer for its icon view. In this case, it might be worth just copy-pasting this specific class and drop the libgd dependency. Sounds worth it setting up an Initiative* to coordinate the port away from libgd. * https://gitlab.gnome.org/GNOME/Initiatives On Tue, Jun 15, 2021 at 11:59 AM Alexander Mikhaylenko via desktop-devel-list wrote: > > As far as I know, libgd is pretty much only used for tagged entries > nowadays. In GTK4 it's a lot easier to implement them in-tree than it > was in GTK3, gtk4-demo even has an example. > > On 15/06/2021 14:54, Allan Day wrote: > > Emmanuele Bassi via desktop-devel-list wrote: > > ... > >> - nautilus > >> - evince > >> - totem > >> - gnome-photos > >> - gedit > > In terms of the platform, we're working to consolidate around > > libhandy/libadwaita. That's what the new HIG documents, and is what > > we're trying to constrain ourselves to on the design side. So it would > > be interesting to know what these apps are using libgd for, and > > potentially track what needs to be done to migrate them away from it. > > I think that it would be beneficial to have our core apps use the same > > platform that we make available to 3rd parties. > > > > > > Allan > > ___ > > desktop-devel-list mailing list > > desktop-devel-list@gnome.org > > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Sign-up to mentor an Outreachy project by September 15
Hi everyone, The GNOME Foundation has confirmed funding for three spots in Outreachy for the December 2021 round! If you would like to mentor this round, please head to https://www.outreachy.org/outreachy-december-2021-internship-round/communities/gnome/submit-project/ as soon as possible and submit your project idea. All project ideas need to be added in the Outreachy’s application system by mentors and approved by the triage committee (Matthias Clasen, Allan Day, and Sriram Ramkrishna) and coordinators (me) by September 15. Because GNOME only usually has a few participants in Outreachy, we are looking to offer projects that are most strategic for GNOME. These include, but are not limited to, projects in the area of privacy, GTK, core experience, core applications, developer experience, and development infrastructure. More information about GNOME’s participation in Outreachy is available at Outreach/Outreachy - GNOME Wiki! . If you have any questions, please feel free to reply to this thread, in our discourse topic*, or e-mail soc-adm...@gnome.org (which is a private mailing list with the GNOME internship coordinators). * https://discourse.gnome.org/t/outreachy-sign-up-to-mentor-an-outreachy-project-by-september-15/7451 Thanks, Felipe Borges. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sign-up to mentor an Outreachy project by September 15
Hi, Just a friendly reminder that if you want to mentor in Outreachy in the December 2021 round, you should submit a project proposal as soon as possible. Cheers, On Fri, Sep 3, 2021 at 9:53 AM Felipe Borges wrote: > > Hi everyone, > > The GNOME Foundation has confirmed funding for three spots in > Outreachy for the December 2021 round! > > If you would like to mentor this round, please head to > https://www.outreachy.org/outreachy-december-2021-internship-round/communities/gnome/submit-project/ > as soon as possible and submit your project idea. > > All project ideas need to be added in the Outreachy’s application > system by mentors and approved by the triage committee (Matthias > Clasen, Allan Day, and Sriram Ramkrishna) and coordinators (me) by > September 15. > > Because GNOME only usually has a few participants in Outreachy, we are > looking to offer projects that are most strategic for GNOME. These > include, but are not limited to, projects in the area of privacy, GTK, > core experience, core applications, developer experience, and > development infrastructure. More information about GNOME’s > participation in Outreachy is available at Outreach/Outreachy - GNOME > Wiki! . > > If you have any questions, please feel free to reply to this thread, > in our discourse topic*, or e-mail soc-adm...@gnome.org (which is a > private mailing list with the GNOME internship coordinators). > > * > https://discourse.gnome.org/t/outreachy-sign-up-to-mentor-an-outreachy-project-by-september-15/7451 > > Thanks, > Felipe Borges. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sign-up to mentor an Outreachy project by September 15
The deadline for mentors to submit projects has been extended to Wednesday, October 6 at 4pm UTC. On Wed, Sep 8, 2021 at 10:42 AM Felipe Borges wrote: > > Hi, > > Just a friendly reminder that if you want to mentor in Outreachy in > the December 2021 round, you should submit a project proposal as soon > as possible. > > Cheers, > > > On Fri, Sep 3, 2021 at 9:53 AM Felipe Borges wrote: > > > > Hi everyone, > > > > The GNOME Foundation has confirmed funding for three spots in > > Outreachy for the December 2021 round! > > > > If you would like to mentor this round, please head to > > https://www.outreachy.org/outreachy-december-2021-internship-round/communities/gnome/submit-project/ > > as soon as possible and submit your project idea. > > > > All project ideas need to be added in the Outreachy’s application > > system by mentors and approved by the triage committee (Matthias > > Clasen, Allan Day, and Sriram Ramkrishna) and coordinators (me) by > > September 15. > > > > Because GNOME only usually has a few participants in Outreachy, we are > > looking to offer projects that are most strategic for GNOME. These > > include, but are not limited to, projects in the area of privacy, GTK, > > core experience, core applications, developer experience, and > > development infrastructure. More information about GNOME’s > > participation in Outreachy is available at Outreach/Outreachy - GNOME > > Wiki! . > > > > If you have any questions, please feel free to reply to this thread, > > in our discourse topic*, or e-mail soc-adm...@gnome.org (which is a > > private mailing list with the GNOME internship coordinators). > > > > * > > https://discourse.gnome.org/t/outreachy-sign-up-to-mentor-an-outreachy-project-by-september-15/7451 > > > > Thanks, > > Felipe Borges. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Colors in tooltips
On Thu, Apr 14, 2022 at 3:01 PM arkkimede via desktop-devel-list
wrote:
>
> Hi!
> I'm developing an application in Gnome using GTK3 + Glade
> I would change the background and the foreground of my tooltips.
> Please, if possible, could you report a css file that implements this
> function?
> I googled and tried a lot of suggestions without success.
> Thank you so much for your help
If you want all tooltips to have the same style, you can define
a CSS style like this:
tooltip {
background: red;
color: blue;
}
If you want tooltips looking different from each other, you can
implement your custom GtkTooltip. See
https://docs.gtk.org/gtk3/class.Tooltip.html
>
> I do not know if this is the right mailing list for those who want to develop
> applications using gtk3 in Gnome. If not, please could you suggest the right
> mailing list.
This mailing list is for discussions related to the development of
GNOME. For application development help, you are better off asking at
https://discourse.gnome.org/c/platform/5
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Moving final mailman lists over to discourse
On Fri, Sep 30, 2022 at 10:29 AM Neil McGovern wrote: > > On Thu, 2022-09-29 at 14:18 -0300, Rafael Fontenelle wrote: > > Hi Neil, > > > > Reading your list-of-lists.txt attachment I noticed that some mailing > > lists used by language teams in Damned Lies are in the "Lists to > > close" category. These mailing lists are used by Damned Lies to send > > notifications of translation activities. If closed there's a chance > > it > > could break Damned Lies notifications, and I don't think Damned Lies > > is not able to notify Discourse. > > Damned Lies can indeed notify Discourse - there's an email interface if > needed, which is what the release team ended up doing. However, I think > a better idea is to rethink the workflow a little... I'll follow up on > the issue :) I agree with Neil here. Discourse doesn't look like the right place for automated notifications. Couldn't Damned Lies allow for translators to individually subscribe for notifications and get these emails sent directly to them? I know this requires someone to implement the feature, but I think it is of our general interest, so maybe we could request some funding for it. In the past we had an Outreachy intern working on integrating GTranslator with Damned Lies, maybe that same intern would be interested in working on this. > > > > > I recommend double-checking that with GTP coordinators. > > > > The language team lists I found in the text file are: > > There's a couple missing from your list (like -cyr) and a couple that > haven't seen postings since 2009 (like -latin), but yes. > > Let's continue over on > https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/325 :) > > Neil > -- > Neil McGovern > Executive Director, The GNOME Foundation > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
