Updates from September, 2007 Toggle Comment Threads | Keyboard Shortcuts

  • Roberto Galoppini 5:18 pm on September 7, 2007 Permalink | Reply  

    OSI Approval: Open Source Initiatives approves GPLv3! 

    Today the GPL v3 and LGPL v3 were unanimously approved by the OSI board, as reported by Michael Tiemann, President of the Open Source Initiative.

    Tiemann blessed the GPLv3 few months ago, and the OSI board this time was really fast to close the GPLv3 approval process, showing a very different attitude compared with an other recent approval.

    I really wish to congratulate with you all!

    tiemannMichael Tiemann by pdcawley

    Tiemann commenting on the OSI blog said he liked to personally acknowledge few people, among them all of us:

    The broader communities of both the free software camp and the open source camps, who both challenged and supported the license drafting process. These communities made the drafts stronger as a result.

    Now it is great time to take into consideration more difficult tasks, and I hope you are definitely not going to follow Eric Raymond line of thinking.

    Despite my previous determination, I find I’m almost ready to recommend that OSI tell Microsoft to ram its licenses up one of its own orifices, even if they are technically OSD compliant. Because what good is it to conform to the letter of OSD if you’re raping its spirit?

    A license is a license, it is definitely not matter of spirit!

    Technorati Tags: GPL, GPLv3, OSI, FSF, MichaelTiemann, EricRaymond, Microsoft

     
    • Martin Peacock 11:58 am on September 8, 2007 Permalink

      You’re right, Roberto, a license is a license. But the objective behind the license is not only to prevent abuse of the spirit, but to defend itself from abuse. If the community at large feels that the OSD is being abused, then it can only be the OSD that is at fault.

    • Roberto Galoppini 5:34 pm on September 8, 2007 Permalink

      Martin,

      I’ll tell you why Eric Raymond opinion is dangerous to the open source ecosystem at large: there are thousands Microsoft’s partners out there, if OSI will allow them to produce (also) open source software is an opportunity, may be even a huge one. If not?

      Besides that, judging licenses’ spirit is a stallmanian attitude, stated by the FSF website, and I really hope to not see things like that happening by the OSI headquarter as well.. Again, licenses are really just licenses, therefore an opportunity not a thread, a medium toward a goal: distributing open source software. If the idea is to keep Microsoft out of the “open source thing”, that is likely what Eric wants, I don’t see the deal.

      Do you?

    • Roberto Galoppini 4:53 pm on September 10, 2007 Permalink

      Stefano,

      a license “technically free” is a free license, and as a matter of fact Microsoft’s channel is the biggest in the IT world. What if only a tiny fraction of them is going to deliver software distributed under a microsoft-approved-free-license?

      About the patent issue, as far as I understand, either if OSI will eventually approve their licenses or not, we have to cope with it anyway.

      Show me the deal we’ll get, if any, if those licenses won’t be approved _because_ submitted by Microsoft.

  • Roberto Galoppini 12:39 am on July 29, 2007 Permalink | Reply  

    Open Source Links: 29-07-2007 

    Where’s the grassroots marketing for Linux? – Alex says that the biggest barrier to Open Source adoption is (poor) marketing, and I share his vision. But appropriating returns from the commons is not trivial, and Open Source firms are not willing to invest huge amount of money to publicize public goods. In my opinion we need to implement unconventional marketing campaigns, spending little money and possibly through a collective action. Consortia and similar organizations could play their role in this respect.

    Open Source at Microsoft – Bill Hilf announced a new web “property” (fix the FAQ page) that outlines Microsoft’s position on OSS, while Port 25 will still be the source for technical issues. Microsoft is getting closer to OSS (SpikeSource certifies OSS on Windows), but I really doubt they are going to buy Red Hat. While I believe that Savio’s analysis is lucid and intriguing, I am afraid that Microsoft’s investors are too IP-addicted, and the 235 patents story tells a lot about how important is to keep them calm. The “cultural” issue is an issue, if we talk about investors, IMHO.

    California city connects with open-source networking – Now it is clear why Cisco is trying to prevent Open Source networking to be successful.

    WHurley spins BMC into open source – Dana mentions Whurley’s experience at BMC, apparently another known hacker is leading the Open Source strategy of a (previously) not OS firm. Just as Bob Bray is doing at Autodesk. Again, when talking about hybrid production model (firm+community) people matter.

    Advertising the open-source way with Openads – Matt met Scott Switzer, Openads’ founder and CTO, to learn more about Openads business model.

    OSCON: Open Source Awards 2007David Recordon won the Open Source Awards 2007 as Best Strategist because he has turned OpenID into a viable alternative to non-open identity systems.

    SourceForge Community Choice Award winners are…. – Matt commenting SourceForge community-driven awards process says that participants had a tenuous grip on what “enterprise” means, may be he is right, and not just green of envy because Alfresco didn’t win! 😉

    OSI Approves New Open-Source License – Ross Mayfield, CEO and co-founder of Socialtext tells eWeek the whole story of the CPAL long approval process.
    The Bug in OSI Approved Licenses – I don’t see any “bug”, besides the partially missing transparency, and VCs’ attitude to invest in OS firms is definitely not an OSI’s issue.

    Intervista a Bruce Perens (Italian) – When Bruce Perens met the blogosphere here in Italy, I happened to interview him, and Nicola Mattina managed to get it published on Nova 24 (Il Sole24 ore).

    [cisco, OSI, Perens, NicolaMattina, BobBray, Whurley, BMC, DavidRecordon, OSCON, commercial open source, open source strategy, Microsoft, SavioRodrigues, SugarCRM]

     
  • Roberto Galoppini 11:04 pm on July 27, 2007 Permalink | Reply  

    Open Source Initiative: badgeware is OSI approved now! 

    Michael Tiemann, President of the Open Source Initiative, recently talking about SugarCRM, SplendidCRM and Centric licenses said clearly that are abusing of the term Open Source:

    THESE LICENSES ARE NOT OPEN SOURCE LICENSES.

    Juggling with feet Always in control by Taomeister

    Today he personally published the Common Public Attribution License: OSI eventually approved badgeware licensing as OSI compliant. Congrats to Bruce and OSI to close this old debate, well done!

    Nowadays one of the open issues has been solved, but the democratic approval process still needs some tuning, since apparently OSI made some last minute changes to the CPAL license.

    Never mind, I agree with Bruce saying that OSI’s approval was a success, but it was slow, and worse he happened to stand up against them just before approving their licenses, something that I can hardly define as opportune. Even if it likely brought SugarCRM to take the decision to adopt the GPLv3, though.

    I am a fan of Open Source Initiative, four years ago I asked my editor to create a logo for my rubric representing also the Open Source mark, but I really wish them being transparent and to react on time.

    Open Source now is ready for prime time, and we need OSI taking is role really seriously, and I suggest them also to consider changing the home page, reporting:

    Open source is a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in.

    The Open Source Initiative (OSI) to me is about maintaining the Open Source Definition, it is a very important task, and it needs to be carried on time and with the highest transparency.

    Technorati Tags: Open Source Definition, tiemann, GPLv3, badgeware, sugarCRM, socialtext

     
  • Roberto Galoppini 8:34 pm on July 13, 2007 Permalink | Reply  

    Open Source License: welcome SaaS, good-bye Free Software! 

    The Free Software Foundation few days ago released the GNU General Public License version 3, as earlier draft versions it doesn’t “fix” the SaaS Loophole, leaving unhappy some entrepreneurs.

    Freedom A Substantial hole, by Rich.w

    While I have already expressed my concerns commenting others’ posts, I believe it is time to tell it straight and loud. In my opinion GPLv3 got on stage too late, now there are simply too many stakeholders to take a decision like closing the GPL Loophole and SaaS could seriously prevent Free Software take over, more than anything else.

    I am not alone, at linux-mag wrote:

    More than the patent protection, more than the digital restrictions, this one change to the GPL could have the biggest impact on the license’s importance in the future.

    Also Tim O’Reilly took a clear position, stating:

    There are both popular and unpopular ways of circumventing the Free Software Foundation’s General Public License. A very unpopular method, we’ve come to find out, is via promises of patent protection for users of specific software. However, if you’re looking to leverage Free Software without completely fulfilling the requirements of the license, a better method would be to exploit the software as a service (SaaS) loophole, which the latest draft of the GPL3 just legalized.

    The Joomla! community has been discussing a lot business model based on the GPL recently. The FSF is cracking “open” door to the SaaS, leaving them – and not only them- a chance to de facto ignore the license.

    A number of people is are happy with the GPLv3, but I am not. This has not been a strategical decision, neither a tactic one, but the only available now. And I blame Richard to postpone it until too late.

    I am really sorry about that.

    Technorati Tags: GPLv3, SaaS, Free Software

     
    • Savio Rodrigues 11:31 pm on July 14, 2007 Permalink

      Hey Roberto, I can totally understand your point of view.

      I’d suggest that any license that attempts to close the SaaS Loophole is going to have an uphill battle. There’s too much code under GPLv2 (and maybe GPLv3 in the future) in use at large SaaS vendors and they’re not going to stand by while the loophole closes. *Or*, if they don’t get in the way of such a license, then these vendors will want the option of paying for the privilege of keeping their modifications private. Sun allows customers to do so with their openJDK project which is under GPLv2. This seems to be the only alternative that large SaaS vendors will accept…at least in my view.

      I ask again, why do OSS proponents love SaaS? 😉

    • Roberto Galoppini 4:55 pm on July 15, 2007 Permalink

      Ciao Savio,

      my point of view comes from my past experience with the FSF community. I have been spending years as FSFE’s friend, and I firmly believe that GPLv3 in 2002 had much more chances to get closer to the Affero. Don’t get me wrong, I think that Richard is a GREAT man, but he did a big mistake, indeed.

      Enterprises, or many of them, do love GPLv2 and now GPLv3. Even some OSS proponents as you pointed it out: OS business models based on SaaS make a lot of sense, as far as we can see. Right?! 😉

    • Chris 10:13 pm on February 2, 2012 Permalink

      “A number of people is happy with the GPLv3, but I am not.”

      Should read

      “A number of people ARE happy with the GPLv3, but I am not.”

      Grammar mistakes anywhere in an article destroy confidence in the rest of it.

    • Roberto Galoppini 7:07 pm on February 5, 2012 Permalink

      Thanks for the note, I updated the article.

  • Roberto Galoppini 11:21 am on June 24, 2007 Permalink | Reply  

    Open Source Links: 24-06-2007 (more about the importance of being called Open Source) 

    Open Source Comedy as Smart Marketing – What about making an Open Source Comedy to tell people about “false” Open Source firms? Between irony and sarcasm there is plenty of space for education through fun

    What makes an open source company: Centric CRM’s response – Michael Harvey gives his explanation of what open source is. Is granting customers the freedom to modify their software or any part of it for internal use enough? I doubt

    Little red hens of open source CRM – Dana Blankenhorn come back talking about the Open Source CRM thing: The value of business software comes out only when you work with it, when you tweak it, when you support it. Absolutely right, s I mentioned few times, there is no third way in this respect: best code or best knowledge.

    Pragmatic Open Source РCot̩ starting from the perennial open source question goes much, much beyond. A must read.

     
  • Roberto Galoppini 9:38 am on June 23, 2007 Permalink | Reply  

    Open Source Links about the importance of being called Open Source 

    Calling Socialtext Open SourceRoss Mayfield, SocialText CEO, asks the community what they should call themselves, while telling us about the experience to get his license certified by OSI.

    Thoughts on OSI, OSD and quasi-open source – Alex Fletcher suggests OSI to proceed constructing (and consistently update) a comprehensive account of the open source which is in violation of its definition of open source, and promote this list to the general community.

    OSI to take more active role in open source definition enforcementRyan Paul at ArsTechinica says that although he sympathizea with OSI’s concern about vendor abuse of the “open source” label, the organization should be above starting a needless fight that it can’t win.

    The OSI crackdown: too little, too late? – Gianugo talking about Tiemann’s position, come out with thr idea of an awareness campaign, making sure that the world knows who’s been fathering the Open Source Definition, and what is not. I buy the idea.

    Micheal Tiemann: Protecting the Open Source Definition – Amy Stephen does some hypothesis about what might happen, food for thoughts.

    Technorati Tags: Open Source, OSI, Tiemann, SocialText

     
  • Roberto Galoppini 7:13 pm on June 22, 2007 Permalink | Reply  

    Open Source Initiative: About the importance of being called Open Source 

    Michael Tiemann, President of the Open Source Initiative, yesterday took a clear position against the abuse of the term Open Source, replying to a Dana Blankenhorn post ” How far can open source CRM get?“.

    I have been on the board of the OSI for more than 5 years, and until last year it was fairly easy for us to police the term open source: once every 2-3 months we’d receive notice that some company or another was advertising that their software was “open source” when the license was not approved by the OSI board and, upon inspection, was clearly not open source. We (usually Russ Nelson) would send them a notice politely telling them “We are the Open Source Initiative. We wrote a definition of what it means to be open source, we promote that definition, and that’s what the world expects when they see the term mentioned. Do you really want to explain to your prospective customers ‘um…we don’t actually intend to offer you these freedoms and rights you expect?’.” And they would promptly respond by saying “Wow! We had no idea!” Maybe once or twice they would say “What a novel idea! We’ll change our license to one that’s approved by you!”. Most of the time they would say “Oops! Thanks for letting us know–we’ll promote our software in some other way.” And they did, until last year.

    It is interesting to see how things change: O tempora, o mores (Alas for the times and the manners).

    So here’s what I propose: let’s all agree–vendors, press, analysts, and others who identify themselves as community members–to use the term ‘open source’ to refer to software licensed under an OSI-approved license. If no company can be successful by selling a CRM solution licensed under an OSI-approved license, then OSI (and the open source movement) should take the heat for promoting a model that is not sustainable in a free market economy. We can treat that case as a bug, and together we can work (with many eyes) to discern what it is about the existing open source definition or open source licenses made CRM a failure when so many other applications are flourishing. But just because a CEO thinks his company will be more successful by promoting proprietary software as open source doesn’t teach anything about the true value of open source.

    Stand up Stand up by groc

    I welcome Tiemann stand up, really. Nonetheless I am among them thinking that Tiemann could hardly enforce his plan, though. My concerns are about the following open issues:

    4. Send your proposed license by email to license-approval@opensource.org. Indicate in the email whether you want the license posted to the license-discuss list with your identification or anonymously. We are willing to consider licenses that the author doesn’t want posted at all, but since community review is an important part of the approval process, we will have to circulate such licenses privately to individual reviewers: because of this, licenses not posted to license-discuss at all may take longer to approve, and are likely to require more interaction with you

    Consider taking a position also on these issues, please.

    Technorati Tags: OSI, Tiemann, attribution, Open Source

     
  • Roberto Galoppini 3:11 pm on June 18, 2007 Permalink | Reply  

    Open Source Business Models: about Joomla going GPL 100% 

    Joomla! announced its committment to fully compliance with the GNU GPL license, a very important step and definitely not an easy decision to take. Joomla!, one of the most popular Open Source CMS platform in fact, is based on the Voluntary Production Model, but it is different from any other projects.

    Freedom Freedom, by cattycamehome

    As I recently happened to know from Amy Stephen, Mambo contributors – and hence later Joomla! contributors as well – were allowed to release proprietary “extensions”, a term used to mean anything you can “add on”. A pretty peculiar characteristic of Joomla! project indeed, and also not an easy issue to address now, as results from the Joomla announcement:

    It’s a long, slow road.We’re not going to make any sudden moves because we know that a lot of people are relying on us to maintain some stability and meet expectations. We are very much aware that a lot of people make their living around Joomla!, and we are sensitive to producing sudden disruptions in livelihoods [..].

    We will provide facts as soon as we have them. If we seem too silent, it’s because we don’t want to speak until we can do so clearly and confidently. And you’ll have plenty of notice before any large changes get made.

    Apparently it is great time to share some ideas about possible directions:

    • Joomla! marketplace: making available all GPL extensions through a vertical marketplace could bring authors consulting opportunities, compensating for fewer deals;
      .
    • Joomla! Enterprises Association: IT firms and individual developers involved with Joomla! could start a business partner network;
      .
    • Re-coding proprietary extensions: Favoured or Popular proprietary extensions could eventually be re-coded allocating funds raised by OpenSourceMatters, if feasible.
      .

    Marketplace.
    Contributors moving from a proprietary licensing scheme to a pure GPL might sell less copies, is a matter of fact. But is their business all about selling proprietary extensions? If this is not the case a vertical marketplace would cover other business areas.

    Enterprise Association.
    Joomla!, as many other Open Source projects, is not a Corporate Actor. As results also from Observatory of European SMBs – see “High Tech SMEs in Europe” – the lack of a coordinator is a known critical success factor:

    For high-tech SMEs (SMB) networks are almost a necessity to perform innovation projects and tap the required information and know-how to conduct business. Networks make possible the sharing of costs as well as risk sharing and contribute to business success.[..]
    The following barriers to networking, specific to smaller high-tech firms, can be identified: (i) Often there is a lack of a ‘co-ordinator’, which might be an agency or a larger leading firm. (ii) Small firms, in contrast to large ones, have a short-term perspective and expect quick and concrete results. [..] To reduce efforts co-operation is kept simple and built with only very few partners. (iii) It is difficult to find a balance between the privacy of information and the necessary knowledge sharing.

    Zope Europe Association, now known as ZEA Partners, is a good example of how a business partner network might work, delivering bigger projects and representing an ‘institutional interlocutor’. Paul Everitt did a very good job with it, indeed.

    Recoding proprietary extensions.
    I guess that only a fraction of Joomla! Extensions are really important to the majority of users and customers. If my assumptions are right, I believe that at the end of the day you might consider recoding only them, asking users to help you prioritizing them.

    A final suggestion about the FAQ:

    What is the difference between “commercial” and “proprietary”?

    Commercial software means that there is some sort of commercial activity surrounding that software. It could be a business that develops it and charges money for distribution, support, documentation, customization, etc. Commercial software is not necessarily proprietary software and proprietary software is not necessarily commercial software. Proprietary software means that you do not have the right to copy, modify, and redistribute that software.

    I would suggest to add that commercial means also something oriented toward profit, and in this respect Commercial Open Source represents a chance to share costs and risks among consumers as well. And yes, a Joomla! Collaborative initiatives might also be a viable option!

    Long life to Joomla, my personal CMS platform of choice!

    Technorati Tags: Commercial Open Source, Joomla, GPL, business model, CMS

     
    • Amy Stephen 4:38 pm on June 18, 2007 Permalink

      Roberto – Thank you for sharing your expertise with the Joomla! community, thanks for your support of Joomla! during this challenging time, too. We benefit from community members like yourself who help solve problems.

    • Roberto Galoppini 5:34 pm on June 18, 2007 Permalink

      Dear Amy, I believe that Joomla! took the right choice, but probably is not going to be easy, though. Joomla! third party developers might experience new business styles: more choices, more chances! Let’s work together to make Joomla! a great business case!

    • Nestor Toothacre 3:21 am on May 22, 2012 Permalink

      Thx for information.

  • Roberto Galoppini 8:12 pm on June 3, 2007 Permalink | Reply  

    Open Source Links: 03-06-2007 

    Free Downloads vs. Sales: A Publishing Case Study – Tim O’Reilly tells an interesting story about Asterisks book, comparing free downloads vs sales.

    IDC values open source software market at $1.8bn – IDC has also predicted that the market will grow by a compound annual growth rate of 26% from 2006 to reach $5.8bn in 2011, by Matthew Aslett.

    Who pays for Open Source? Freemium conversion rates – Don Dodge correlates “Freemium” conversion rates to the ratio of OSS users paying for support contract. IS that a general rule? I doubt.
    How to select a CMS -  Seth Gotlieb wrote an insightful post about CMS selection, James McGovern commented and Seth eventually noticed that only some OS products have vendors behind them. The process, in this case, might be different.

    Alfresco and Liferay User GroupAlfresco and Liferay are hosting a CMS/Portal user group meeting in Ontario, Carlifornia on Wednesday July 18th.

    Microsoft and IronRuby – John Lam on IronRuby.

    Office 2.0 Conference Redux – The Office 2.0 Conference will be held in S.Francisco next September, if interested fill the registration form at discount price until July 14.

    Novell Open PR: ‘Last call’ draft of GPLv3 – GPLv3’s stakeholders and loopholes are still driving the draft review process.

     
  • Roberto Galoppini 7:05 pm on May 24, 2007 Permalink | Reply  

    Open Solutions Alliance: Sartorio unveils OSA’s strategy 

    The Open Solutions Alliance (OSA) debuted recently with a strong emphasis on promoting interoperability among open source software solutions, and its membership was supposed to be open to organizations providing open source solutions. Dominic Sartorio – OSA’s President – few days ago stepped by and eventually get engaged in a interesting discussion with me about Open Solutions Alliance’s strategy.

    Oblique Strategy Oblique Strategy by gualtiero

    At the OSA (Open Solutions Alliance), we have a diverse membership and are often asked what we consider to be “open” business models. So, we track this issue with great interest.

    Inevitably, discussion goes down the path of licensing, or how strong each member’s community it. What isn’t discussed enough, IMO, is what best meets customer needs.[..] Because open source, especially in the applications space, is still relatively new, we think there is much room for experimentation regarding what business models are best for the most customers. Consequently, we don’t limit our membership based on some preconceived notion of business models we think ought to be the best.[..]

    I have been pretty critical about OSA’s decision to accept members not using open source licenses, calling them “false positive” , but reading Dominic’s comment I learned that there is one notion that they don’t compromise, namely the degree of openness:

    We fundamentally believe that open and collaborative behavior is consistently superior to closed and unilateral behavior. This difference go beyond how the source code is managed, to how the company fundamentally operates; How it engages with its customers and partners, its corporate marketing, and even corporate culture and internal politics.

    I replied suggesting to be clear about it, and tell everyone that OSA has decided not to talk about open source, while now the logo itself reports “open source at work”. I invited OSA to avoid to make open source definition uncertain, considering make some adjustments to the website, reporting:

    From time to time, the OSA may use the term “open source solutions” or “open source based solutions.” We do not mean to confuse this with the OSI’s Open Source Definition, which includes requirements not included in our open solution definition.

    Dominic come over again, below his full comment.

    Hi Roberto, Thanks for your thoughtful reply. Yes, we had our own “false start” through sloppy use of the term “open source” when we originally launched last winter. Open Source (capital ‘O’, capital ‘S’) means something very specific, as defined by the OSI, and the OSA intends to cover broader ground, for the reasons I described in my previous post. Our collective experience has been that customer value can be achieved in a variety of ways, and some of them don’t always fit a strict definition.

    You found other parts of our website that we overlooked. Thanks for finding this, and we will fix this. We don’t intend to cause further ambiguity around what it means to be “open source”, but rather clarify an issue that we believe hasn’t received enough attention: focus on customer needs. In an effort to avoid confusion, we came up with our own term, “Open Solution Definition” (PDF).

    Rest assured that our continuing work on this issue will be done in fully open and collaborative ways. Just like open and collaborative development has led to great Open Source products, we believe that open collaboration by the vendor community on various business issues is the best way to achieve customer success.

    Many vendors are incapable of this behavior. Some grew during the pre-WWW time when business success depended on unilateral behavior and “knowledge hoarding” than the collaborative behaviors that modern technologies now enable. Take a look at a more recent blog re: the Microsoft patent issue as an example.

    Searching for “Open Source” occurrences I noticed that among the actual members only two out of 19 don’t mention open source in their presentations. Apparently OSA is building a stack of open source products – where I see Red Hat RHX more credible offering open source stacks – and a stack of open source services. The latter hypothesis sounds more interesting, OSA would be the first to exploit the potentialities of open source firms taking advantage of the absence of a Corporate actor.

    Technorati Tags: Commercial Open Source, RHX, Open Solutions Alliance, Sartorio

     
    • Dominic Sartorio 1:00 am on June 1, 2007 Permalink

      Hi Roberto,
      Interesting ideas. We have a lot of product vendors among members, but mostly products whose success depends on horizontal services being relatively standard in the industry (integration, management and monitoring, project management, reporting, content management, and broadly-scoped business applications such as ERP, all depend on best practices for various services). We are also starting to attract more “integrator” members, who don’t represent an open source product themselves but focus on support and professional services. So, your observation appears to be proving itself out in practice, and I would expect the OSA to focus on these areas in the future.

    • Roberto Galoppini 3:36 pm on June 2, 2007 Permalink

      Dominic, I guess that OS firms with “vertical” offering won’t apply if among OSA’s members someone else has already a similar offer. So, at some point you might consider that one database is not enough, but could you bring in any other?
      I can hardly see other OS database firms investing in a common brand-oriented strategy, because appropriating returns sounds uncertain. Dominic, go for focusing, go!

c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel