Milagro: October's podling update

Hey all, I just submitted October's report to the wiki, due by EOD today: https://cwiki.apache.org/confluence/display/INCUBATOR/October2023#milagro Enjoy the rest of your day Riccardo

CVE-2023-33241 and resolution

Hello everyone, you might have woken up to the news of a vulnerability affecting, among other things, Apache Milagro's MPC implementation https://www.cve.org/CVERecord?id=CVE-2023-33241. Thanks to a confidential disclosure the vulnerability has been fixed since commit

Re: Podling Milagro Report Reminder - April 2023

Hi Justin, I will submit it in the next few hours. Sorry for the delay! Riccardo On April 12, 2023, jmcl...@apache.org wrote: > Hi, > > Is the project planning on submitting a report? If so, please submit > it within the next 24 hours. > > Kind Regards, > Justin

Re: Pycon Milagro presentation.

Hi Giorgio, glad to know you want to help spread the word! I believe that it is everyone's responsibility to talk about all of the great things we are doing here and I am glad you want to take some of that up. Even though people employed by Qredo Ltd are active contributors to the project, and

Re: change name of repo

Hi, I think it makes 100% sense, to get naming closer to Apache conventions. +1 Riccardo On Tue, 28 Feb 2023 at 09:14, Kealan McCusker wrote: > > Hi All > > I propose that we change the name of this repo > > https://github.com/apache/incubator-milagro-MPC > > to > >

Changing default branch for the Milagro repositories

Hi, within the community of the Milagro (incubating) project, we would like to make some adjustment to the default branch setup of our project, to simplify the workflows. However, the only documentation I found on how to do that has been this one, which I have no idea how to run:

Mapping our path towards graduation

Hi all, I have spent some time to map our path towards graduation, to get a pulse of where we are at, and what we are still missing. This is the result: https://github.com/orgs/apache/projects/171/views/7 I interpreted definitions of the readiness framework conservatively and I tried to err on

Re: Porting the website to Docusaurus 2

On December 12, 2022, Riccardo Iaconelli wrote: > Hi all, > > I recently ported the current website to Docusaurus 2. This is a major > update that leapfrogs two major versions (the current is based on > version 0.x). Hi! The PR is now merged and the new website is live!  Riccardo

Porting the website to Docusaurus 2

Hi all, I recently ported the current website to Docusaurus 2. This is a major update that leapfrogs two major versions (the current is based on version 0.x). A preview is accessible here: https://incubator-milagro.vercel.app/ I'm glad to say that with this update we solve all of the security

Re: Apache Milagro status

Hello Jean-Frederic, On Tue, 1 Nov 2022 at 10:51, jean-frederic clere wrote: > On 10/31/22 19:09, Riccardo Iaconelli wrote: > > I think we already respect many of the criteria there, at least for the > > technical side (reproducible builds, code quality...) and that we can &g

RE: Apache Milagro status

Hey Giorgio, On 2022/10/27 09:42:20 Giorgio Zoppi wrote: > Hello, > I have questions: > How can we promote this work to give to this project > the success that it deserves? The MPC library is very promising. > How can we get the TLP project status? > Best Regards, > Giorgio I'm also interested

Re: archive

Dear Kealan, On 2022/10/28 15:33:11 Kealan McCusker wrote: > Hi All > > I propose to merge develop into master and from now on use master as the > default branch > for these repo's; > > https://github.com/apache/incubator-milagro-crypto-c > https://github.com/apache/incubator-milagro-MPC >

[jira] [Resolved] (MILAGRO-40) Linked Travis CI is not accessible

[ https://issues.apache.org/jira/browse/MILAGRO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riccardo Iaconelli resolved MILAGRO-40. --- Resolution: Fixed > Linked Travis CI is not accessi

[jira] [Commented] (MILAGRO-40) Linked Travis CI is not accessible

[ https://issues.apache.org/jira/browse/MILAGRO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602187#comment-17602187 ] Riccardo Iaconelli commented on MILAGRO-40: --- Thanks for your help, the job has been completed

[jira] [Comment Edited] (MILAGRO-40) Linked Travis CI is not accessible

[ https://issues.apache.org/jira/browse/MILAGRO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601782#comment-17601782 ] Riccardo Iaconelli edited comment on MILAGRO-40 at 9/8/22 12:10 PM

[jira] [Commented] (MILAGRO-40) Linked Travis CI is not accessible

[ https://issues.apache.org/jira/browse/MILAGRO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601782#comment-17601782 ] Riccardo Iaconelli commented on MILAGRO-40: --- updates – with the help of [~johnmcw] we managed

[jira] [Updated] (MILAGRO-40) Linked Travis CI is not accessible

[ https://issues.apache.org/jira/browse/MILAGRO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riccardo Iaconelli updated MILAGRO-40: -- Attachment: image-2022-09-08-14-03-25-110.png > Linked Travis CI is not accessi

[jira] [Updated] (MILAGRO-40) Linked Travis CI is not accessible

[ https://issues.apache.org/jira/browse/MILAGRO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riccardo Iaconelli updated MILAGRO-40: -- Description: Hi,   the [current README|https://github.com/apache/incubator-milagro

[jira] [Commented] (MILAGRO-40) Linked Travis CI is not accessible

[ https://issues.apache.org/jira/browse/MILAGRO-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600658#comment-17600658 ] Riccardo Iaconelli commented on MILAGRO-40: --- Thanks [~jfclere] ! the URL is linked

[jira] [Created] (MILAGRO-40) Linked Travis CI is not accessible

Riccardo Iaconelli created MILAGRO-40: - Summary: Linked Travis CI is not accessible Key: MILAGRO-40 URL: https://issues.apache.org/jira/browse/MILAGRO-40 Project: Milagro Issue Type: Bug

[jira] [Commented] (MILAGRO-39) upgrade swagger ui

[ https://issues.apache.org/jira/browse/MILAGRO-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580986#comment-17580986 ] Riccardo Iaconelli commented on MILAGRO-39: --- should be closed now! > upgrade swagger

[jira] [Commented] (MILAGRO-39) upgrade swagger ui

[ https://issues.apache.org/jira/browse/MILAGRO-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578345#comment-17578345 ] Riccardo Iaconelli commented on MILAGRO-39: --- thanks, I just asked for a merge to the asfsite

[jira] [Commented] (MILAGRO-39) upgrade swagger ui

[ https://issues.apache.org/jira/browse/MILAGRO-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576172#comment-17576172 ] Riccardo Iaconelli commented on MILAGRO-39: --- Hi, I created a PR with the update here: [https

Introducing myself + facilitating an MPC release

Hi all, I joined a few weeks ago the mailing list (you might have seen some of my learning pull requests coming along, too) and I would love to briefly introduce myself to you all. My name Riccardo Iaconelli, I've been a KDE developer for over 15 years, a Mozillian for 5, and throughout my

Re: Hello from MyGNUHealth

further help. > > > > A presto! > > Luis > > > > > > > > On Tue, 5 Jan 2021 17:32:18 +0100 > > Riccardo Iaconelli wrote: > > > > > Hi Luis, > > > > > > that is amazing news!! > > > Would you consider

Re: WikiToLearn status

P.s. On t.me/wtleditnotification you will find a bot notifying of all recent edits. This could be a great starting point to assess the situation. If the community wants to help please feel free to poke me on Matrix (@ruphy:KDE.org) or via mail Riccardo Il dom 14 feb 2021, 17:58 Christoph

Re: WikiToLearn status

Hi Christoph, You pinged us yesterday afternoon, please consider daily jobs and life outside KDE, and if possible wait at least a couple of days before assuming the project is dead. The project is still active indeed, even if clearly not as explosively growing as in 2016-2017. To this, the

Re: Hello from MyGNUHealth

Hi Luis, that is amazing news!! Would you consider adding a PublicCode to your repo? It's a metadata format for indexing and providing a catalog of open source solutions to Public Administrations You can find an online editor here: https://publiccode-editor.developers.italia.it/ and more info on

Re: Help with KDE PIM and Google Privacy Policies needed

On venerdì 6 marzo 2020 07:40:49 CET Martin Flöser wrote: > And reading the screenshot I think that's the problem. We state in our > privacy policy about 3rd party plugins and Akonadi. Especially Akonadi > is a "transfer of data to others" and that allows all applications to > access the data.

Re: Retirement of notes.kde.org

Hi Ben, On lunedì 16 settembre 2019 08:03:31 CEST Ben Cooksley wrote: > The content of notes.kde.org will be exported - likely in ODT format - > prior to us shutting it down. > The resulting files will be made available on share.kde.org. > > If there are things which need to be resolved prior to

[kirigami] [Bug 382685] New: Android: pressing back with the global drawer open results in the application closing

https://bugs.kde.org/show_bug.cgi?id=382685 Bug ID: 382685 Summary: Android: pressing back with the global drawer open results in the application closing Product: kirigami Version: unspecified Platform: Other

Re: KDE at FOSDEM 2017 wrapup

I also gave away about 500 stickers I bought from moo.com - they were cheap and nice, lots of people were taking it! Bye, -Riccardo On 15 February 2017 at 16:17, Jonathan Riddell wrote: > I also gave away £113 worth of KDE stickers I bought from > handylabels.co.uk. These

Re: KDE Licensing Policy Updates

On 23 September 2016 at 18:52, Luigi Toscano wrote: > Still, as I mentioned, it would introduced problems if we move documentation > forth and back from wikis to other formats, and also with mixing content from > older documentation. I still don't buy the "cumbersome"

Re: [kde-community] possible foss alternative to telegram/slack

Hi, On 18 July 2016 at 16:58, Filipe Saraiva wrote: > If there is some interest in this test, please let me know and I can > foward the reply for them. at WikiToLearn we set up a test instance on one of our staging servers. You can login with phabricator details on

Re: [WikiToLearn] [kde-community] Please participate in our survey for input on KDE's Mission

Hi, On 28 June 2016 at 23:50, Sven Brauch wrote: > I trust you are aware of the biasing the amount of participants from the > different areas introduces and aim to provide the results of the poll in > a form which is transparent with respect to this bias. I guess we will

Re: [kde-community] [WikiToLearn] Please participate in our survey for input on KDE's Mission

Hi, On 28 June 2016 at 23:50, Sven Brauch wrote: > I trust you are aware of the biasing the amount of participants from the > different areas introduces and aim to provide the results of the poll in > a form which is transparent with respect to this bias. I guess we will

[Differential] [Updated] D1844: Add Appinfo metadata file

ruphy edited reviewers, added: Visual Design Group; removed: WikiToLearn: Visual design and promo. REPOSITORY rPLASMADESKTOP Plasma Desktop REVISION DETAIL https://phabricator.kde.org/D1844 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: jriddell, mak,

[kde-community] WikiToLearn getting in touch Mozilla's network of ambassadors

Hi all, I have recently met Daniele Scasciafratte, a Mozilla representative, at a conference in Albania. He's a long time KDE fan, and when he learned about WikiToLearn he thought it was a fantastic idea to promote through the Firefox Students Ambassadors program. Here's one thread he opened

Re: [Wikitech-l] [MediaWiki-announce] Security Release: 1.26.3, 1.25.6, and 1.23.14

Sent from my mobile phone, please excuse any typos. Il 20 mag 2016 7:08 PM, "Chad" ha scritto: > I would like to announce the release of MediaWiki 1.26.3, 1.25.6 and > 1.23.14. > > These releases fix sixteen security issues in core, one issue in the > bundled >

Re: [kde-community] Telegram Relay Service

On sabato 7 maggio 2016 18:23:10 CEST Myriam Schweingruber wrote: > I wonder why nobody > examined this POV before starting to shift to Telegram. In this regard > Mattermost appears to make much more sense as we could run it on our > own servers, if we really need a phone client. Speaking as

Re: [kde-community] KDE Mission - let's do this!

Hi, On 24 April 2016 at 21:34, Alexander Neundorf wrote: > Nevertheless a comment about the "end-user webservices": AFAIK OwnCloud and > WikiToLearn are quite different. OwnCloud is a developing a software, while > WikiToLearn is mainly about creating content (for a MediaWiki).

Re: [kde-community] KDE Mission - let's do this!

On 12 April 2016 at 01:13, Thomas Pfeiffer wrote: > From what I see on the wiki, there are three questions we should try to answer > first: > > 1. Should the mission focus mostly on our organizational/community strategy, > our product strategy, or both? I think we should

Re: KDE file dialog

On 28 February 2016 at 20:06, Aleix Pol wrote: > The string is in Qt, AFAIR. It probably can't be changed until Qt 6 if > we don't want to mess with existing installations. We should still probably alias it and deprecate 'kde', so that people can start using the right name

Re: KDE file dialog

On 28 February 2016 at 15:58, Luigi Toscano wrote: > > This is what I use: > export QT_QPA_PLATFORMTHEME=kde (btw, shouldn't this be "plasma"?) -Riccardo -- Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平 Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini

Re: [kde-community] finding a clear vision for KDE - second draft for discussion

On Wednesday, February 17, 2016 07:37:07 PM Ingo Klöcker wrote: > "KDE creates technology for a world in which everyone has freedom, > privacy and control over their digital life." > > isn't a conflation of vision and mission. I wondered whether the actual > vision isn't just the second part,

Re: [kde-community] finding a clear vision for KDE - an alternative draft for discussion

On Tuesday, February 16, 2016 10:12:06 AM Mario Fux wrote: > As I see it the "graphical user interfaces and applications" (which is an > enumeration of different paradigms/things anyway could/should be > substituted with "software" and there would be an agreement more or less > between the two

Re: [kde-community] Wikis uneditable

On 16 February 2016 at 15:01, Ingo Malchow wrote: > Most of the needed parts are already done. What is still missing is the > login, > which should be based on Oauth2 over phabricator. If you have any knowledge > about this, or some code flying around, feel free to send it over

Re: [kde-community] Wikis uneditable

Il 16 feb 2016 8:35 AM, "Ben Cooksley" ha scritto: > > > > PS: Any update on possible solutions for the wikis? > > It's a work in progress, requiring a full Mediawiki update and all the > challenges that implies. > Do you want to move parts of it within WikiToLearn and our

Re: [kde-community] finding a clear vision for KDE - first draft for discussion

On 11 February 2016 at 22:06, Alexander Neundorf wrote: > so do I understand correctly that in general you would consider projects > like > a shell, a compiler and a text-mode editor as potential KDE projects ? > I honestly still find it strange that in this discussion we

Re: [kde-community] finding a clear vision for KDE - first draft for discussion

On Tuesday, February 09, 2016 09:24:43 PM Lydia Pintscher wrote: > But more seriously: Wikimedia's vision doesn't say that all the > knowledge has to be with Wikimedia - just that it must be universally > and freely accessible. ... which is, incidentally, the reason why they have been helping us

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Friday, February 05, 2016 08:40:21 AM Alexander Dymo wrote: > You > can satisfy all the requirements in the manifesto, but still be a bad > candidate for a KDE project. As the extreme example, one could fork > Plasma and want to join KDE. There are less extreme cases. I wonder why you say that

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Thursday, February 04, 2016 08:53:57 AM Alexander Dymo wrote: > Let's say it wants to join KDE. Under the > "inclusive" proposal such a project will be welcomed. Under "focused" > - no. The vision document will never be a metric to accept or refuse a project. The manifesto is the only

Re: [kde-community] Differences between proposed vision drafts (or "inclusive" vs "focused")

On Friday, February 05, 2016 08:01:49 AM Alexander Dymo wrote: > As Lydia put it, it will be a clear frame of reference to make > choices in. No way. Quoting Ben Cooksley: This criteria has already been laid out by the KDE Community, in a document called the Manifesto. It lays out fairly

Re: [Wikitech-l] Announcing mediawiki-containers, a Docker-based MediaWiki installer

On Thursday, December 24, 2015 03:57:50 PM Gabriel Wicke wrote: > I am writing to announce mediawiki-containers [1], a simple installer for > MediaWiki with VisualEditor, Parsoid, RESTBase and other services, using > Linux containers. Hi Gabriel, we at WikiToLearn have automated all of our

Re: [kde-community] Sprint: Reorganize the wikis

On Thursday, December 10, 2015 02:53:25 PM Varun Joshi wrote: > Hi, > If there's any way I could help, I'd like to participate (remotely) too! We'll post updates and definitely make sure you guys are involved! :-) ping me if we're too silent! -Riccardo

Re: [kde-community] Sprint: Reorganize the wikis

On Monday, December 07, 2015 01:11:22 PM Olivier Churlaud wrote: > So should I create a doodle? Or open a forum and put the link here? And > how do we organize the discussion ahead to plan everything? Forum or ML? > > How much time ahead should it be prepared? I mean: what is reasonable > for a

Re: [kde-community] GCi start is beginning soon: Dec. 7

On Monday, November 30, 2015 07:16:47 PM Valorie Zimmerman wrote: > As of right now, we have 44 tasks. That is about 130 fewer than > Staphanie recommends. We've never fallen short before, and I believe > that we won't this time either. But without Freenode for the past few > days, I feel very

Re: [Wikitech-l] Introducing WikiToLearn to developers

On Sunday, November 29, 2015 11:37:40 AM Pine W wrote: > Could we meet on Thursday, 3 December at 10 AM PST / 7PM CEST, or Monday, 7 > December at 10 AM PST / 7PM CEST? > > I'm fine with this being an open "office hour"-like environment where anyone > can join the conversation on Hangouts. I'm

[Wikitech-l] Introducing WikiToLearn to developers

Hi all, I would like to introduce to the Wikimedia community WikiToLearn, a FOSS project of which I am a participant and which is lately getting a lot of contributions and momentum. It is a KDE project sponsored (among the others) by Wikimedia Italy and recently joined by institutions such as

Re: [Wikitech-l] Introducing WikiToLearn to developers

On Friday, November 27, 2015 09:07:39 AM Brad Jorsch wrote: > How does it compare to Wikibooks? From the description it sounds very > similar. Or Wikiversity? Wikibooks is mostly for "generic" books, while we aim at content with a didactical value. For this reason we don't want the restrictions

Re: [Wikitech-l] Introducing WikiToLearn to developers

On Friday, November 27, 2015 08:04:17 PM Federico Leva wrote: > To clarify, Wikimedia Italia doesn't financially sponsor this site nor > contribute content to it. AFAIK our volunteers provided some MediaWiki > training to the site's users. Wikimedia Italia is always happy when > MediaWiki usage

Re: [Wikitech-l] Introducing WikiToLearn to developers

On Friday, November 27, 2015 04:05:25 PM Ricordisamoa wrote: > What a better proof that itwikiversity has failed. > But it is getting restarted > > recently. We should definitely get in touch and join forces :-) -Riccardo

Re: [Wikitech-l] Introducing WikiToLearn to developers

On Friday, November 27, 2015 04:15:09 PM Pine W wrote: > This sounds like a wonderful project for the Wikimedia universe. It also > aligns with the interests of the education interests of multiple US > affiliates. Would you be able to set up a Hangout meeting with some of us > (me and whoever else

Re: [Wikitech-l] Introducing WikiToLearn to developers

On Friday, November 27, 2015 08:32:50 PM Brad Jorsch wrote: > If I can trust Google Translate, it.wikibooks.org's equivalent pages say > roughly the same thing. Hi Brad, what I meant is that we create various forms of text, and most content might not be directly unitary textbooks, but simply

Re: [kde-community] Leaving KDE community

On Monday, November 02, 2015 09:21:33 PM Gustav González wrote: > The latest months I wasn't in the mood even to answer some mails mentioning > Tupi in this list, so I chose to wait for the right moment to send this > message, and I think it is today. > > The KDE community is great and I really

Re: [kde-community] Fwd: [FOSDEM] FOSDEM 2016: Call for Participation

On 22 October 2015 at 13:56, Pau Garcia i Quiles wrote: > The devroom has been confirmed. We will publish a call for talks in week. > I have submitted my KDE talk as a keynote or main track. Is there any overlap? Bye, -Riccardo -- Pace Peace Paix Paz Frieden Pax Pokój

[kde-community] Submitted a a KDE Talk at FOSDEM 2016

Hi all, I just submitted a WikiToLearn talk at FOSDEM this year, as I anticipated. I asked for a keynote slot, let's see if I get it or it gets moved to the main track... ;-) Here's title, subtitle and abstract: Bringing academia to the Internet era - How open textbooks will change teaching and

Re: [kde-community] Fwd: [FOSDEM] FOSDEM 2016: Call for Participation

Just FYI, I plan on submitting a talk... I am not sure what I could need help with, but in case you have ideas, please reach to me :-) -Riccardo Il 28/set/2015 09:19 AM, "Lydia Pintscher" ha scritto: > Hey folks :) > > Pau was awesome and already requested the devroom and stand

Re: [kde-community] Official KDE mirror on github in the light of the KDE manifesto

On 25 September 2015 at 23:33, Albert Astals Cid wrote: > AFAIR last time we tried gitlab it crawled under "KDE size" scenario, so > unless it has improved it would not work with KDE + more stuff. should we try to get more powerful machines...? ;-) -Riccardo -- Pace Peace Paix

Re: [kde-community] Official KDE mirror on github in the light of the KDE manifesto

On Thursday, September 24, 2015 07:35:41 PM Valorie Zimmerman wrote: > I really do not want the excellent parts of this impassioned > discussion to get lost! We've wondered about it before, and perhaps it > is time to look at this issue again. A web ui? I think that more and more github should be

Re: [kde-community] Official KDE mirror on github in the light of the KDE manifesto

On Friday, September 25, 2015 01:16:46 PM Jaroslaw Staniek wrote: > e.g. Gitlab? It is more freedesktop.org... The software is not a problem (gitlab for that works amazing), but I was more looking to two points: * a real a community hosting (not https://about.gitlab.com/terms/ ) * more

Re: [kde-community] Help for sprint guidance/organization

On Saturday, September 19, 2015 04:17:11 PM Martin Klapetek wrote: > so I haven't really organized any sprints myself but have participated > in many, some good, some less good. So here's my personal take > on this speaking from experience: Thanks, it was really appreciated! For those wondering,

Re: [kde-community] What is a GitHub pull request exactly?

On Sunday, September 20, 2015 06:39:02 PM Bhushan Shah wrote: > We don't need to replace Facebook.. tada. > > Facebook is not part of our development nor anything.. So lets not > compare with facebook.. When we talk about github and do our reviews > there. It will be recorded there and if github

Re: [kde-community] Write our own pull request bot?

On Sunday, September 20, 2015 10:50:43 AM Martin Klapetek wrote: > Gnome in their years history of github mirroring had 4 pull requests > (it was mentioned in the other thread...one of the others). > > So we might very likely be talking non-issues here anyway. 100% agreed -Riccardo

Re: [kde-community] What is a GitHub pull request exactly?

On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote: > Free software needs free tools. I am sorry, but sadly this is not the state of the art. KDE has been created with many non free tools and currently co-exists in many non-free environments. We can either decide to live with it and

Re: [kde-community] Write our own pull request bot?

On Sunday, September 20, 2015 02:39:53 PM Loïc Grobol wrote: > IIRC the main argument was not laziness, it was discoverability. But > if we have a nice wiki page to guide people in the switching process, > it should be relatively painless. In any way, we can still try and see > if the issue

Re: [kde-community] What is a GitHub pull request exactly?

On Sunday, September 20, 2015 01:51:19 PM Laszlo Papp wrote: > I just do not happen to see this case strong enough to support, > personally. We have not even tried to see how the mirror works out, > and we already think of whether or not it is a big problem not > allowing pull requests, et al. It

Re: [kde-community] What is a GitHub pull request exactly?

On Sunday, September 20, 2015 03:01:09 PM Luigi Toscano wrote: > Riccardo Iaconelli ha scritto: > > On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote: > >> Free software needs free tools. > > > > I am sorry, but sadly this is not the state of the art. KDE h

Re: [kde-community] What is a GitHub pull request exactly?

On Sunday, September 20, 2015 03:01:09 PM Luigi Toscano wrote: > Riccardo Iaconelli ha scritto: > > On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote: > >> Free software needs free tools. > > > > I am sorry, but sadly this is not the state of the art. KDE h

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, September 19, 2015 04:24:13 PM Eike Hein wrote: > Developer recruitment should be our #1 problem for the > next two years, and along those lines "GitHub might get > us contributors" is by far the strongest argument that > side's come up with. Somebody once defined Github as the

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, September 19, 2015 10:58:09 AM Michael Pyne wrote: > Is anyone actually arguing this point in the way you ask? No one's asking > to prevent "one offs" entirely, the core of the issue is that KDE > development should happen *within* KDE-the-whole-community, not *apart > from* KDE.

Re: [kde-community] Official KDE mirror on github

On Saturday, September 19, 2015 04:26:04 PM Luigi Toscano wrote: > But that's not using the pull request. Such workflow would mean that the > pull request is not accepted anyway, but the code is pushed through the > infrastructure and not trough Github interface. > > Just to be sure, question for

Re: [kde-community] Write our own pull request bot?

On Saturday, September 19, 2015 01:17:18 PM Martin Klapetek wrote: > To further expand on the idea, the workflow would be as follows: > > * bot looks through our repos > * bot finds a pull request > * bot downloads the diff between requested branch and mirror HEAD > * bot uploads it to

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, September 19, 2015 05:47:38 PM Martin Graesslin wrote: > On Saturday, September 19, 2015 5:32:33 PM CEST Kevin Krammer wrote: > > If the problem is somewhere in (a), where is it? > > I'm afraid of code review happening through the pull request instead of our > infrastructure. To me

[kde-community] Help for sprint guidance/organization

Hi all, (hoping to break the thousands of emails currently being written...) we're having our first sprint at WikiToLearn!!! It's an exciting news since most of the participants are absolutely newcomers to FOSS development (let alone to KDE), and to various degrees to WikiToLearn too. The

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

I understand the takeover concern, it is a valid point. If I become the maintainer of application X, which was accepting pull requests, and I don't want to have a github account, I either have to create an account, find somebody on the team who wants to monitor pull requests, or change the

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, September 19, 2015 06:44:24 PM Martin Graesslin wrote: > No reality would be that it slowly moves code review from KDE to github. And > I think we have here quite some people in the discussion who would love to > see that I don't think anyone ever thought that... o.o -Riccardo

Re: [kde-community] Official KDE mirror on github

On Saturday, September 19, 2015 02:12:13 AM Albert Astals Cid wrote: > > I would prefer us to be more pragmatic. If an adequate free-software > > tool exists, lets try to use it. If a proprietary tool provides a > > better experience lets use that. For my own projects I will advocate > >

Re: [kde-community] Official KDE mirror on github

On Friday, September 18, 2015 11:43:34 PM Vishesh Handa wrote: > It depends on our end goal: creating free software or creating free > software with only free tools? If it is the latter then I fear we have > already failed since many of us use additional tools to aid > development which are not

Re: [kde-community] FOSDEM Organisation

On 7 December 2014 at 18:15, Carl Symons carlsym...@gmail.com wrote: * Get on with it. John's not attending and not bringing equipment that has been used in the expo space in past years. Who can pick up the slack? What would be needed? A WikiFM contributor is currently studying and living in

Re: [kde-community] Incubating project

Hi! It's Italian only for now as here is where we found a community of users and content producers, and since most content is initially coming from course notes, typing them in LaTeX is one thing, typing + translating them is another. ;-) As Jeremy was explaining, I'm very open to have other

Re: GSoC update from Riccardo - his KMail is b0rked again

Hi, On Monday 20 August 2012 14:53:47 Matěj Laitl wrote: Such code should live in a branch until it has general feature parity (in this case: functionality of all meaningful applets that work reliably currently should be provided by the new CV: wikipedia, labels, lyrics, similar artists,

Re: GSoC update from Riccardo

On Tuesday 21 August 2012 16:07:27 Matěj Laitl wrote: Hey, this is actually a good (and constructive) proposal! From my PoV I would: * Move Labels to Level 0 (I use the applet often, plus people are more more getting used to using tags for example in Dolphin IMO) - but feel free to introduce

news from GSoC

Hi, during the GSoC, I've been working on a draft document to describe a little bit my vision for a next UI of Amarok. It's not final, it's still a work in progress, it's a draft, and blablabla, but with all those disclaimers, I thought that it might interest somebody around here, so here it

GSoC report

Hi, just a quick note to follow up the weekly schedule: this week i've been busy with upcoming exams, and so I haven't done a real lot. I will start committing to Amarok (in a branch) soonish. Bye, -Riccardo ___ Amarok-devel mailing list

GSoC report #2

Hi, time for the weekly report! Unfortunately, I've not achieved too much this week since there has been a pretty big midterm exam (which will happen tomorrow by the way), so I've only continued working on the UI mockups. I will propose a semi-final version for feedback as soon as it is ready,

Introduction; GSoC report

Hi, I would like to introduce myself to this list, I'm Riccardo Iaconelli, a KDE developer who this year happens to be a GSoC student who will work on Amarok. As you might or might not know, know, I will work on the context view and on sexying up Amarok's UI. I've started my GSoC coding

[Bug 259949] Kmail does not use all addressbooks for autocompletion

https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #63 from Riccardo Iaconelli riccardo kde org 2012-02-07 11:53:47 --- So, while at FOSDEM, I've asked PIM developers in person, and it looks like yes, this bug is going to be fixed very soon. This bug looks like a side effect of another

[Bug 259949] Kmail does not use all addressbooks for autocompletion

https://bugs.kde.org/show_bug.cgi?id=259949 Riccardo Iaconelli ricca...@kde.org changed: What|Removed |Added CC||ricca...@kde.org

[Bug 259949] Kmail does not use all addressbooks for autocompletion

https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #29 from Riccardo Iaconelli riccardo kde org 2011-10-18 12:21:45 --- (p.s.: looking more deeply in the description of this bug, i had the same symptoms of #277403, which might or might not be related) -- Configure bugmail: https

  1   2   3   >