05.03.09

Gemini version available ♊︎

Gnote Enters Fedora

Posted in GNOME, GNU/Linux, GPL, Microsoft, Mono, Novell, Red Hat at 2:05 pm by Dr. Roy Schestowitz

Fedora (hat)

Summary: Gnote will be included in Fedora 10 and Fedora 11, which is out shortly

THE developer of Gnote moved to Fedora a few days ago. Fedora is known for its realisation and insistence on Freedom (although it does not go far enough for some). A lot of this is caused by legal precaution and Fedora already blocks Moonlight for this reason alone.

Gnote is a perfectly acceptable application which performs gracefully. According to this conversation, “The Fedora project further confirms this [that Gnote is fine] by including Gnote in Fedora 10 and 11.” Moreover: “Gnote is GPLv3-or-later, so it can always be distributed under the terms of the latest version of the GPL.”

“Gnote is a perfectly acceptable application which performs gracefully.”The pro-Mono crowd (some Novell and Microsoft employees included) would not be terribly happy about this because Tomboy is admittedly not as libre as Gnote. Jo Shields says that “[f]eatures CANNOT be ported back from Gnote – Gnote is GPLv3, and is only compatible with LGPL2 in one direction. I suspect this was 101% intentional.”

Irrespective of whether it’s intentional or not — and apparently it’s not even true — Gnote grew tremendously fast (even its resistors are stunned by how much was achieved in less than a month) and it's pending addition to Debian and Ubuntu. For those who want GNOME to stay independent from Mono, Gnote [1-6] is a project to support by spreading the word and asking distribution packagers to include it (either installed by default or added to the repositories).
____
[1] Project of the Day: GNote
[2] Tomboy is Afraid of Gnote, Its Mono-free Sibling
[3] Gnote Supports 6 More Languages, Does Not Support C#
[4] The Role of Mono and Moonlight Revisited
[5] Did Tomboy Learn from TomTom? Project Forked, Moves Away from Microsoft ‘Standards’
[6] Novell Partners Promote Silverlight, Zeitgeist at Risk of Mono(polists)

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

11 Comments

  1. a said,

    May 3, 2009 at 9:23 pm

    Gravatar

    “Gnote grew tremendously fast (even its resistors are stunned by how much was achieved in less than a month)”

    Well, it’s not particularly hard to transcribe code from one language to another. You’re really just limited by how fast you can read the C# and write the corresponding line in C++. There’s very little thinking required.

  2. Jose_X said,

    May 4, 2009 at 1:33 am

    Gravatar

    [Thinking defensively for a minute]

    I worry that most of what might be patented in the csharp version would still be affected in the c++ version (at least initially). I would rather avoid gnote for the reason that its core design comes from the environment restraints imposed by dotnet .. Ie, it’s possible we are witnessing a submarine attack.

    The odds of avoiding dotnet related patents should grow over time as more changes are made to the c++ version. The problem is that the key properties that might violate a patent in the mono version, might still be there in gnote. Worse would be if the author was working intentionally to guide gnote such as to remain in violation as gnote grew in features and popularity.

    I’d prefer something else be used instead of gnote, with gnote used only by those that want to get weaned off the mono version. It’s safer taking this approach, especially since gnote appears to be so similar to its parent in design.

    If we were witnessing a submarine attack, it would be more effective than the efforts with mono because it would be sneaking in under any radar that was going to judge only based on the mono label. People might then even help the app out more than usual, thinking they were getting “even” with the mono project. I could even see the original mono authors faking being upset.

    Any application can be started by individuals working in concert with patent owners (as proxies to bypass the GPL). I don’t know if the GPLv3 would stop this. Perhaps the GPL could add in a clause saying “to the best of my knowledge, my contributions do not violate any patent.” Even in this case, we would not be protected, but at least someone would be on the hook (a deterrence) to help defend against fraud and sabotage.

    I’d prefer to see a project managed by a group that would adopt such a clause (independent of the GPL) as a requirement from the author of any changes to the project’s code.

    As an aside, please considering writing to your government representatives explaining the foolishness of software patents. These do not promote the progress of science and useful arts.

    Roy Schestowitz Reply:

    The problem is that the key properties that might violate a patent in the mono version, might still be there in gnote.

    I’m not sure that I agree. To use an analogy, if someone has a patent on rubber, than making a car with wheels may be hard, but making a boat shouldn’t. Boats don’t ‘interface’ much with rubber.

  3. Jose_X said,

    May 4, 2009 at 6:15 am

    Gravatar

    >> To use an analogy, if someone has a patent on rubber, than making a car with wheels may be hard, but making a boat shouldn’t. Boats don’t ‘interface’ much with rubber.

    This analogy basically says that you can make a note application that avoids a mono-ish patent [build a boat that avoids rubber (let's assume)]

    What I am saying is that this immediate port that is gnote is still likely mostly the original boat that was made with rubber, except that the color and the way the rubber holds and various other things may have changed some (or the equipment used to make the boat is different, but it’s still a similar boat).

    In short, gnote can become safe of what plagues a mono app, but I’m not confident gnote is at that level or will be allowed to be taken to that level.

    A more direct example is that a hypothetical mono-ish patent might cover various arrangement of objects or methods that are a part of mono/dotnet. If these are very core obj/meth, then we’ll say that almost any mono app would be in violation.

    Now, convert a mono app to c++ without re-architecting, and you likely are still using the same obj/method arrangements (organization), except that you used a different language to blueprint these. The final product still would be constructed or function possibly just as the patent describes.

    It’s not a matter of “can gnote be made safely” but one of “will gnote be made safely”. This is difficult to answer unless you could know all the patents that might apply. Not knowing that, the best is not to start with a mono based design. Doing so is risky. Finally, I worry the lead dev might work to maintain the violations [not accusing anyone, but that is a worry].

  4. Jose_X said,

    May 4, 2009 at 7:42 am

    Gravatar

    Here is a positive. Some of the patents might be with things that happen in the background when you use mono. Cutting out enough of that “managed” framework, might get you off the hook.

    Please write to your government reps saying how foolish and stupid the patent system is when applied to software. http://boycottnovell.com/2009/04/13/acta-leaks-ip-wars/comment-page-1/#comment-61915
    http://boycottnovell.com/2009/04/16/rms-software-patents-eu/#comment-62024

    Jose_X Reply:

    I submitted the wrong version of the comment by accident.
    ******
    Here is a positive (I’d hate to ignore the positives since there may be no subterfuge involved here).

    Some of the patents might be with things that happen in the background when you use mono (very dotnet-ish things). Cutting out enough of that “managed” framework, might get you off the hook.

    Please write to your government reps saying how foolish and stupid the patent system is when applied to software. Software patents are creating undeserved riches for a few at the cost of much to many.

    http….

    Roy Schestowitz Reply:

    I’m a little more pessimistic. As much as I wish to believe that people influence policies, I doubt congresspeople will turn a deaf ear to corporations that buy laws for software patents and other protections like DMCA.

  5. Robert said,

    May 4, 2009 at 8:40 pm

    Gravatar

    Has roots in mono? Just say no… very easy!

    I do not think there is a safe path by which to connect the babie’s room and the snake pit – all discussion of relative merit is just words – just say no!

    And with respect to Jose_X – that would only apply in a nation where law rules, and where the people had representation – that, unfortunately is no longer murka…

  6. r_a_trip said,

    May 5, 2009 at 8:13 am

    Gravatar

    I think we need to step back here just a little. If the patents in DotNet are worded in such a way, that they lay claim to a note taking app, then all note taking apps violate DotNet patents.

    DotNet, like java, is a virtual processor with a virtual instruction set that can be fed with corresponding machine code. The neat trick here, is that it can be potentially WORA (Write Once, Run Anywhere), if you make the virtual processor available on multiple platforms. The only new addition MS put in DotNet in comparison to Java is language independence. You can mix and match modules written in different languages.

    Most patents in DotNet likely pertain to the way the CIL interacts with the CLR and how you can compile different languages to CIL. These don’t interact with an independent program like a note taking app. The structure of Tomboy is dictated by its functionality, not on which platform it runs. Cut the physical machine independence (CLR) from the executable and most of the DotNet patents go poof.

    Translating the C# code to C++, makes Gnote native and removes the DotNet language dependence. In essence Gnote has now become like any other app. It can violate patents, but not because development started on DotNet. The DotNet link has been severed.

    Then we still have the ruling in Re: Bilski. This ruling severely damaged the basis for Software Patents. It very well might be that software Patents are dead,but they don’t know it yet.

    Roy Schestowitz Reply:

    Sun recently tried the Bilski DefenseTM without success.

    Check out this from the news.

    the11thplague Reply:

    Agree with this. Mono is a problem because it deals with a patented language, C#. Stop using Mono, and you are safe from C# patents.
    Patents about programs in general will sill be a danger, as they are for any software, open or not. Even M$ got hit by software patents.
    Really, no program is completely safe, so Gnote can be just “safer” by using GPL3 and not using Mono (which is likely to be a C# trap).

DecorWhat Else is New


  1. Links 22/10/2021: Trump's AGPL Violations and Chrome 95 Released

    Links for the day



  2. [Meme] How Corporate Monopolies Demonise Critics of Their Technically and Legally Problematic 'Products'

    When the technical substance of some criticism stands (defensible based upon evidence), and is increasingly difficult to refute based on facts, make up some fictional issue — a straw man argument — and then respond to that phony issue based on no facts at all



  3. Links 22/10/2021: Global Encryption Day

    Links for the day



  4. [Meme] Speaking the Same Language

    Language inside the EPO is misleading. Francophones Benoît Battistelli and António Campinos casually misuse the word “social”.



  5. António Campinos Thinks Salary Reductions Months Before He Leaves is “Exceptional Social Gesture”

    Just as Benoît Battistelli had a profound misunderstanding of the concept of “social democracy” his mate seems to completely misunderstand what a “social gesture” is (should have asked his father)



  6. IRC Proceedings: Thursday, October 21, 2021

    IRC logs for Thursday, October 21, 2021



  7. Links 21/10/2021: MX Linux 21 and Git Contributors’ Summit in a Nutshell

    Links for the day



  8. [Meme] [Teaser] Miguel de Icaza on CEO of Microsoft GitHub

    Our ongoing series, which is very long, will shed much-needed light on GitHub and its goals (the dark side is a lot darker than people care to realise)



  9. Gemini Protocol and Gemini Space Are Not a Niche; for Techrights, Gemini Means Half a Million Page Requests a Month

    Techrights on gemini:// has become very big and we’ll soon regenerate all the pages (about 37,500 of them) to improve clarity, consistency, and general integrity



  10. 'Satellite States' of EPO Autocrats

    Today we look more closely at how Baltic states were rendered 'voting fodder' by large European states, looking to rubber-stamp new and oppressive measures which disempower the masses



  11. [Meme] Don't Mention 'Brexit' to Team UPC

    It seems perfectly clear that UPC cannot start, contrary to what the EPO‘s António Campinos told the Council last week (lying, as usual) and what the EPO insinuates in Twitter; in fact, a legal challenge to this should be almost trivial



  12. The EPO’s Overseer/Overseen Collusion — Part IXX: The Baltic States

    How unlawful EPO rules were unsurprisingly supported by Benoît Battistelli‘s friends in Baltic states; António Campinos maintained those same unlawful rules and Baltic connections, in effect liaising with offices known for their corruption (convicted officials, too; they did not have diplomatic immunity, unlike Battistelli and Campinos)



  13. Links 21/10/2021: GIMP 2.99.8 Released, Hardware Shortages, Mozilla Crisis

    Links for the day



  14. How Oppressive Governments and Web Monopolists Might Try to Discourage Adoption of Internet Protocols Like Gemini

    Popular movements and even some courageous publications have long been subverted by demonisation tactics, splits along unrelated grounds (such as controversial politics) and — failing that — technical sabotage and censorship; one must familiarise oneself with commonly-recurring themes of social control by altercation



  15. [Meme] Strike Triangulations, Reception Issues

    Financial strangulations for Benoît Battistelli‘s unlawful “Strike Regulations”? The EPO will come to regret 2013…



  16. [Meme] Is Saying “No!” to Unlawful Proposals Considered “Impolite”?

    A ‘toxic mix’ of enablers and cowards (who won’t vote negatively on EPO proposals which they know to be unlawful) can serve to show that the EPO isn’t a “social democracy” as Benoît Battistelli liked to call it; it’s just a dictatorship, currently run by the son of a person who actually fought dictatorship



  17. IRC Proceedings: Wednesday, October 20, 2021

    IRC logs for Wednesday, October 20, 2021



  18. [Meme] EPO Legal Sophistry and Double Dipping

    An imaginary EPO intercept of Administrative Council discussions in June 2013...



  19. Links 21/10/2021: PostgreSQL JDBC 42.3.0 and Maui Report

    Links for the day



  20. [Meme] [Teaser] “Judge a Person Both by His Friends and Enemies”

    Fervent supporters of Team Battistelli or Team Campinos (a dark EPO era) are showing their allegiances; WIPO and EPO have abused staff similarly over the past decade or so



  21. 'Cluster-Voting' in the European Patent Office/Organisation (When a Country With 1.9 Million Citizens Has the Same Voting Power as a Country With 83.1 Million Citizens)

    Today we examine who has been running the Finnish patent office and has moreover voted in the EPO during the ballot on unlawful "Strike Regulations"; they voted in favour of manifestly illegal rules and for 8.5 years after that (including last Wednesday) they continued to back a shady regime which undermines the EPO's mission statement



  22. The EPO’s Overseer/Overseen Collusion — Part XVIII: Helsinki's Accord

    The Finnish outpost has long been strategic to the EPO because it can help control the vote of four or more nations; evidence suggests this has not changed



  23. [Meme] Living as a Human Resource, Working for Despots

    The EPO has become a truly awful place/employer to work for; salary is 2,000 euros for some (despite workplace stress, sometimes relocation to a foreign country)



  24. Links 20/10/2021: New Redcore Linux and Hospital Adoption of GNU Health

    Links for the day



  25. IRC Proceedings: Tuesday, October 19, 2021

    IRC logs for Tuesday, October 19, 2021



  26. Links 19/10/2021: Karanbir Singh Leaves CentOS Board, GPL Violations at Vizio

    Links for the day



  27. [Meme] Giving the Knee

    The 'knee' champion Kratochvìl and 'kneel' champion Erlingsdóttir are simply crushing the law; they’re ignoring the trouble of EPO staff and abuses of the Office, facilitated by the Council itself (i.e. facilitated by themselves)



  28. Josef Kratochvìl Rewarded Again for Covering Up EPO Corruption and the EPO Bribes the Press for Lies Whilst Also Lying About Its Colossal Privacy Violations

    Corrupt officials and officials who actively enable the crimes still control the Office and also the body which was supposed to oversee it; it's pretty evident and clear judging by this week's press statements at the EPO's official Web site



  29. [Meme] Sorry, Wrong Country (Or: Slovenia isn't Great Britain)

    Team UPC is trying to go ahead with a total hoax which a high-level European court would certainly put an end to (if or when a referral is initiated)



  30. How Denmark, Iceland, Finland, Norway and Sweden Voted on Patently Unlawful Regulations at the EPO

    We look back and examine what happened 8 years ago when oppressed staff was subjected to unlawful new “regulations” (long enjoyed by António Campinos, the current EPO autocrat)


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts