05.03.09

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

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

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).

What Else is New


  1. 'Ethical Source' is Not Ethical and Not a Movement But a Misguided Self-Serving PR Stunt

    Something which is neither enforceable nor ethical is being promoted by profoundly unethical media in the pockets of large corporations



  2. InteLeaks – Part XXI: Intel Seeking Advice From a Bunch of Clowns (Harbor 'Research')

    A firm called Harbor 'Research' is making dubious recommendations to Intel; as shown in the above video, there's also an obsession with buzzwords (typically suggestive of a lack of technical grasp/understanding)



  3. IRC Proceedings: Monday, January 18, 2021

    IRC logs for Monday, January 18, 2021



  4. The US Election Was Not Rigged, But the Nomination Process Was (Undermined to Maintain Control by Oligarchy)

    Cheating/driving the left out of the Democratic Party seems like a longstanding tradition and we know who stands to gain from it; moreover, problems remain in the voting process because it's controlled by secret code of companies like Microsoft (in spite of the openwashing)



  5. InteLeaks – Part XX: Redacted (for Names Only) Release of Intel File About Developer eXperience (DX) Meddling in GNU/Linux

    Today (or tonight) we release the first 'phase' of InteLeaks in a sensibly redacted form; coming up next is a surprise from Team Microsoft



  6. Sites in Bed With the EPO and UPC 'Covering' the 'News' Without Mentioning Any of the Overt Abuses

    It is rather sad that blogs like IP Kat have turned into proponents of abusive EPO management and Team UPC increasingly resorts to lying using pseudonyms (to avert criticism and accountability); much of the rebuttal or response that’s hinged on reality/facts can only be found in comments, which are still subjected to a face-saving moderation process (conducted by Team UPC)



  7. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part IV: Stories From the Depths of the Free Software Foundation (FSF)

    To reduce or alleviate suspicions and a potential of mistrust the FSF needs to become more transparent and liberate information (such as the real reason Bradley Kuhn left, as noted in the previous part)



  8. Links 18/1/2021: GNU Radio 3.9, Wikipedia at 20

    Links for the day



  9. InteLeaks – Part XIX: Intel's Web 'Experts' Seen as Microsoft Champions Dealing With the Platform Microsoft is Looking to Destroy

    Things aren't rosy at Intel because the hires aren't suitable for the job of documenting and/or presenting GNU/Linux-centric products (whose target audience is Free software developers)



  10. Adding Images as Characters to the Daily Bulletins of Techrights

    Our daily bulletins now have inside them coarse graphics, depicted using characters alone, and the tool used to generate them announced a new release earlier today; we showcase some of its features (in a new video)



  11. Links 18/1/2021: Weekly Summaries and Linux 5.11 RC4

    Links for the day



  12. IRC Proceedings: Sunday, January 17, 2021

    IRC logs for Sunday, January 17, 2021



  13. The Oligarchs' Parties Will Never Choose the Side of Software Freedom Because Free Software Cannot Bribe Officials

    The tough reality is that next week's (or this coming week's, depending on what Sunday counts as) inauguration ceremony is partly symbolic as all the same and important issues remain largely untouched, for corporations control almost everything of significance



  14. COVID-19 Has Actually Helped Software Freedom Due to Financial and 'Spare Time' Factors

    Developers and users are increasingly exploring what the Free software world has to offer; this is actually measurable and it contradicts claims to the contrary



  15. Future Plans and Using Videos to Complement Text

    Remarks on recent and impending site changes; We are not replacing text with video, we're just trying to enhance the presentation a bit, especially where visuals help make a point or where browsing through Web sites (or leaks) is more suitable than static, linear presentation



  16. InteLeaks – Part XVIII: Intel Does Not Know How to Properly Do Research and It Seems Apparent Unscientific Methods Are Used to Justify Poor Documentation

    There appears to be a severe crisis at Intel; they cannot recruit scientists (or those whom they recruited are walking away) and as a result the company produces bad products with poor documentation (or highly defective chipsets that top-notch marketing cannot compensate for); in this video we walk through some examples of how studies are being conducted (as already noted in Part XVII)



  17. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part III: The Free Software Foundation (FSF) Seems More Like a Victim of Destabilisation Campaigns

    The Free Software Foundation (FSF), which turns 36 later this year, is looking to raise money that helps support the GNU Project, soon 38 years old and likely the most important Free software project to exist (ever)



  18. Links 17/1/2021: EasyOS on Raspberry Pi and GNU libsigsegv 2.13

    Links for the day



  19. InteLeaks – Part XVII: The High Cost of Microsoft Windows Users in GNU/Linux Development Teams

    A look inside Intel explains what holds back the technical team, which bemoans the lesser technical people getting in the way and not even using the product that they are writing about



  20. IRC Proceedings: Saturday, January 16, 2021

    IRC logs for Saturday, January 16, 2021



  21. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part II: Why Bradley Kuhn Left the Free Software Foundation (FSF)

    The founder of the FSF is still at the FSF (albeit not publicly) and the person who lobbied to oust him has basically been 'banished' by the founder



  22. Links 16/1/2021: LibreOffice 7.1 Release Candidate, Zeroshell 3.9.5, FreeBSD Report, and GhostBSD 21.01.15

    Links for the day



  23. Free Speech on the Web Not Respected by Companies That Used to Support Software Freedom

    Mozilla does not have to make its Web browser about politics; it can just make an excellent piece of software that is neutral about the Web pages that it renders, based on the user's personal preferences



  24. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part I: We Are Under Attack by Corporations and Their Salaried Facilitators

    The corporate takeover (taking over the Commons, produced by volunteers who are motivated by altruism) is a subject we must speak about and somehow tackle; this series will highlight uncomfortable or difficult truths



  25. InteLeaks – Part XVI: Intel Cannot Do Command Line, Even When It's Vastly Simpler and More Suitable for Development

    The Developer eXperience (DX) team at Intel seems to be full of Microsoft drones instead of developers and/or mildly technical people; this has not only harmed the quality of documentation but also upset staff, alienating people who actually understand what developers need (more than buzzwords like "DX")



  26. IRC Proceedings: Friday, January 15, 2021

    IRC logs for Friday, January 15, 2021



  27. Links 15/1/2021: KaOS 2021.01, Whisker Menu 2.5.2, Istio 1.8.2

    Links for the day



  28. InteLeaks – Part XV: Intel is Blind to Blind and Colour-Blind People

    Intel does not seem to grasp very basic concepts associated with accessibility; nevertheless, Intel shamelessly tries painting itself as "woke" and a "justice warrior" (policing speech while overlooking much-needed practical work)



  29. Links 15/1/2021: GStreamer 1.18.3 and Proton 5.13-5

    Links for the day



  30. IRC Proceedings: Thursday, January 14, 2021

    IRC logs for Thursday, January 14, 2021


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