Recent Updates Page 102 Toggle Comment Threads | Keyboard Shortcuts

  • Roberto Galoppini 9:00 pm on May 26, 2007 Permalink | Reply  

    Open Source Franchising: From artisanship to industrial 

    Years ago I happened to cut my hair by a Jean Louis David salon, and once understood how simple was to choose my hairstyle from a brochure, I never tried another barbershop. Jean Louis David could inspire any wannabe open source Franchisor.

    Barbershop Barbershop by Joel Aron

    Jean Louis David in the 60s changed the world of the hairdressing, inventing modern cutting techniques using clippers, eventually starting an international salon brand, now famous all over Europe. It was a revolutionary idea, since barbershops and hairdressers were artisans delivering personal services, at some extent unreplaceable.

    Speaking with a managing director of a franchisee, I learned about the training they receive, preparing them to achieve any kind of cut using clippers, but also about opening manual razor’s packaging in front of customers (in order to show them that are new).

    When we need a haircut we do know what we want, we also know how long it should take, and we can easily judge if the shop meets our cleaning standards. In a word, we are educated clients.

    Nicole France, formerly Gartner’s analyst, wrote:

    IT has been and largely still is an artisanal craft, part skill and part black magic. Most organisations of any size have had to create their own IT departments, not so much out of desire, as of necessity.

    So while IT Providers must still raise the bar on delivering reliable IT services, ensuring also legal compliance, IT Customers should better understand the benefits and tradeoffs involved in focusing on (predictable) results. In this respect there is a tremendous need for marketing actions.

    An Open Source Franchisor could be aimed at delivering to the market IT basic services using OSS, with a fixed-time fixed-price formula, training its franchisees to meet predefined performance criteria.

    Open Source franchising for customers could eventually become a shortcut to get reliable solutions, and as seen with Geeksoncall there is plenty of space for growing in computer services franchise arena.

    The International Franchise Association, an organization devoted to enhancing and safeguarding the business environment for franchisors and franchisees worldwide, recommends the following when considering franchising:

    • Demand: Is there a demand for the franchisor’s product or services in your community? Is it seasonal or does it generate repeat business? Will there be continuing demand for the product or services in the future, is it temporary or a fad?
      .
    • Competition: What is the level of competition, nationally and in your community? How many company-owned outlets does the franchisor have in your area? How many competing companies sell the same or similar products and services?
      .
    • Location: Is it located in the inner city? What are the demographics? Is this particular type of business needed in your community?
      .
    • Name Recognition: Is the company’s name widely recognized? How long has the franchisor been in operation? Does the company have a good reputation?
      .
    • Training & Support: What backgrounds do the current franchise owners have? Do they have prior technical backgrounds or special training that helps them succeed? Do you have a similar background?

    The demand for these services is still partially unexepressed, and need to be stimulated, while on the other side we might consider there is no competition in this respect, yet.

    A strong Brand is important, and that’s why my perfect franchisor is Sun.

    Training will make the difference, moving from artisanship to industrial has never been too easy, though.

    Technorati Tags: commercial open source, business model, franchising, jean louis david

     
  • Roberto Galoppini 2:54 pm on May 25, 2007 Permalink | Reply  

    Open Source Links: 25-05-2007 

    Ubuntu Dells – Derek Buranen did price comparison of the cheapest Dell desktop compared to a Windows-loaded version of the same specs.

    Open Source CMS offers great benefits to scientific collaborative researchThe new ZEA partners talks about the potential of collaborative software for research within EU projects.

    HP looks to expand open source services – is HP about to sell legal and license compliance services?

    Briefing analysts on open source – Alex Fletcher provides some tips on briefing analysts on open source.
    Microsoft goes open source for identity Microsoft has started four open source projects to aid interoperability between identity management systems.

    Novell to publish more details of Microsoft agreement – Novell will publish more details on its collaboration agreement with Microsoft before the end of May.

     
  • 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!

  • Roberto Galoppini 12:33 pm on May 23, 2007 Permalink | Reply  

    Open Source Business Models: the Beekeeper model 

    James Dixon, Pentaho Chief Technology Officer, commenting a post introduced me to the “Beekeeper model“, a model used by open source firms writing the majority of the code.

    BeeKeeper Beekeepers (private) parking by Phil Downsing

    The Bee Keeper mode, which applies to companies like Pentaho, Alfresco or Zimbra, is about open source products where the original author, a company, is the main (if not the only) source code contributor (corporate production, in my words).

    Going through the whole document (PDF), I found interesting Dixon’s observations about the different kind of professional open source (commercial open source) firms looking at them by the relationship with the code:

    • Passive / Committers: Did not write much, if any, of code themselves. They provide services and support for third party open source software. They do not have their own community.
      .
    • Outers: Code started as proprietary software and has been released into open source by the creators.
      .
    • Founders: Originated project to be professional open source from the start. Often need seed capital to achieve this.
      .
    • Converters: Started project as open source project without intent to make money from it. Added ways to make income from it after it became successful. These are sometimes small businesses. Examples: JFreeChart.
      .
    • Baiters: Released an open source project as a method to attract consumers to a different, proprietary piece of software. Examples: Actuate BIRT.

    What is missing is a taxonomy describing how Professional Open Source firms cope with their communities, and how (and if) their business models are affected by the relationship.

    I suspect that Converters examining later which business model would be right for them have lesser choice, nevertheless they have a community and they can get advantage of it.

    About Outers, I believe that a taxonomy of the reasons to give away software would reveal something really interesting. The reason affects how and if the software will eventually be developed in cooperation with a community (hybrid production).
    Founders are also intriguing, whether they belong to the “third wave” (applications), or are exploring business models based on the absence of a corporate actor, why VCs are interested in investing in open source software firms would be important too. I guess that VCs play a very important role in the community start-up process.

    Technorati Tags: Beekeeper, business model, Commercial Open Source, Dixon, Pentaho

     
    • Debbie Moynihan 10:12 am on May 27, 2007 Permalink

      This is interesting. I hadn’t seen this list of business models before – thanks for sharing it. I attended OSBC this week where several different models were discussed. One thing that I find most interesting is how everyone seems to continuously evolve their business models over time as they figure out what works. I am hoping to get my notes from OSBC posted in the next 24 hours or so onto my blog.

      Deb

    • Roberto Galoppini 11:20 pm on May 28, 2007 Permalink

      Hi Debbie,

      unfortunately I couldn’t join OSBC this year, so I am eager to know more about it, please.

      About business models I believe that OS market is young enough to keep changing, because it is fundemental true that:

      In the beginner’s mind there are many possibilities, but in the expert’s there are few (Shunryu Suzuki-Roshi)

  • Carlo Daffara 5:11 pm on May 21, 2007 Permalink | Reply  

    Open Source Adoption: OpenTTT, testing the IRC approach on open source 

    Choosing the best open source products is considered one of the biggest challenges in open source adoption. Software selection costs are so high that specialized consulting companies are doing it as their main job, see Optaros and Spikesource just to name two of. Why is it so difficult?

    Juggler Choose by Dovaneh

    There are many reasons:

    • there is no single place to search for OSS (sourceforge hosts a significant percentage of projects, but some merely started there and then moved elsewhere; there are many other forge-like sites and many software listing sites like freshmeat).
      .
    • there is no consistency in the software evaluation; even models like OSMM and BRR have many components that are based on human evaluation, and some more recent approaches even change the evaluation model and forms depending on the software area or market.
      .
    • there are many excellent projects that are not widely known; a great example is the large and sophisticated packages in the scientific software area, virtually unknown outside of a small community).

    This means that only a few projects get any visibility, and that many useful tools are not employed even when they could be the perfect match for a company. On this consideration, the EU funded a small project called OpenTTT, that tries to apply a “matching model” to help in the adoption process.

    It works like this:

    • A group of companies and public administrations are audited, and a set of needs in terms of software and IT functionalities are collected in structured forms (using a modification of the original IRC forms, called TR or technology requests);
      .
    • in parallel, OSS companies and developers are invited to fill a complementary form indicating on what projects they are offering services;
      .
    • requests are grouped, whenever possible, to find a single match for multiple companies;
      .
    • a manual matched process is performed to find potential matches between requests and offers matchmaking is perfected in one-to-one personal meetings at special “matchmaking” events;
      .
    • one has been recently performed at CeBIT and another at the CONFSL conference.

    An interesting twist of OpenTTT, that we hope to start soon, is the “club” concept. After all matches are performed, we expect that some needs will go unfulfilled; in this case we will try to find a “near match”, and try to group users with the same need into user clubs, and forward the information that an unfulfilled need has been identified to the groups of developers. After this, users and developers or companies are free to negotiate a commercial agreement, for example for implementing the missing pieces.

    See a chart depicting the process.

    I hope that this model can be a basis for a more structured and “grassroot” model for interaction between users and developers, not only because it gives an explicit recognition of the fact that OSS is not about price (at least not only about that) but also about flexibility and matching the user needs in a better way.

    Technorati Tags: OpenTTT, confsl, best practice, IRC

     
  • Roberto Galoppini 12:28 pm on May 20, 2007 Permalink | Reply  

    Commercial Open Source is a Juggling act (part II) 

    Commercial Open Source has a lot in common with Juggling, and once you have broken the problem down into simpler steps, it is up to your discretion what to do next.

    Juggler Absentmindedly juggling by T Bell

    In juggling balance is an essential skill, but it doesn’t equal to stillness.

    The downside of balance is that you don’t want things to change. The moment you’ve achieved balance, you’d better be ready and willing to get rid of it. Because if you stay with what you think is perfect balance, you’ll be far from in control. Remember, there is no perfect balance; there’s only the approach to it.

    Open sourcing your software – throwing the balls – it is just the very first step, then you started playing you need to continuously refine your technique. Look at Funambol, now playing with two “balls” (community and carrier edition) instead of three: they are keeping moving and refining their business model. So does Alfresco, GPLing its software in order to give its new hybrid community a chance – and here I see a need for major adjustments, if they really want it to be a multiple vendors’ project.

    Juggling is also about being flexible to the unexpected:

    flexible to mistakes of any kind, like the wrong music coming up.When the unexpected flares up, you have to have a sense of humor — to know that your position has been compromised. It’s not the end of the world.

    May be at Novell they didn’t expect what’s going to happen because of the so-called nefarious deal, but it took ages for them to “catch” it, and the public get annoyed by not-so-humorous tricks. They were not proficient also in the “show-ending“, eventually.

    Open Source firms have to juggle different types of things, and the different characteristics of the objects affects your business game.

    Worse than dropping objects is letting them collide in the air and fall in random patterns. To prevent this, you need to create a separate flight path for each object. This comes from training and from knowing how objects move. A ring is a thin planar object that can slide through the air. A club creates a much bigger planar area as it revolves on its axis, and it takes up a lot more space. Then there’s the ball — the easy one that flits in and out of space. But the funny thing is that it’s usually the ball that screws everything up.

    Persons are like balls, if your business is based upon a community-based resource you really need to pay a lot of attention to retain them: a weak intellectual property asset need care.

    Customers are like clubs, the Internet it is just to small, and customers’ satisfaction gets more and more important when (and if) the exit cost is small. Despite the buzz can greatly help to get new users and eventually customers, but then you need to keep listening them.

    Partners are like rings, quite difficult to throw, but once in the air they are consistent with the original trajectory, unless you try to juggle them under wind conditions. Once you get partners, they tend to stay.

    And you better know that numbers jugglers do their best just with rings!

    Michael Moschen, one of greatest living jugglers, was interviewed by Anna Muoio, a Fast Company‘s journalist who wrote an inspirational article entitled “Life is a Juggling act“. I grabbed some idea from the original article – that I would recommend if interested in the subject – to talk about Commercial Open Source and Juggling.

    Technorati Tags: commercial open source, juggling, moschen

     
  • Roberto Galoppini 6:44 pm on May 19, 2007 Permalink | Reply  

    Open Source Links: 19-05-2007 

    Business as Usual – Bill Hilf on Port25: It’s not us versus the free world.

    Three Minutes with Microsoft’s Open-Source Manager – Bill Hilf explains Microsoft strategy: to license and not litigate. Am I the only one thinking to the Cold war at this stage?

    235 more reasons to love open source – Fabrizio Capobianco designed a funny and provoking t-shirt, and I guess he is going to bring along an XXL one for Bill Hilf next Monday!

    Steve? Darl? All of the Above? – Billy Marshall asserts that Microsoft won’tl like the nature of the collateral damage caused by the 235 move.

    (added on the 20th) Microsoft’s Patent Impasse – A lucid commentary by Cote’, really enlightening.
    Organizing an Open Source Workshop!!! – A workshop entitled “Open Source, Open Ideas” will be held on Tuesday May 29th at the Politecnico di Bari campus sponsored jointly by Politecnico di Bari, OrgLab (University of Cassino), Syracuse University and IESEG School of Management.

    Dell announces the models for Ubuntu – Jeremy discloses Dell’s Ubuntu models.

    I’m Joining Adobe – Ryan Stewart joined Adobe as a Rich Internet Application Evangelist.

     
  • Carlo Daffara 6:40 am on May 18, 2007 Permalink | Reply  

    Open Source Blueprints: replicable experiments in open source adoption 

    Is there a better way for helping companies and public administrations in the OSS adoption process? Most adoptions are based on a few different paths, for example by grassroots adoption, from consultancy intervention, by trying to replicate a known success story. In this sense, the concept of “best practice” can be considered as a way to tell others of something that worked well, but in the past it has not been successful in replicating the experience.

    Best Practices Best Practices by andai

    So, considering that most public administrations are pushing for initiatives to help the adoption process (even if it mainly means creating another forge – like the Italian one just launched – I would like to propose the concept of the “implementation blueprint” as an
    extension of the best practice model. The idea came out of our experience in the
    Open TTT project, that is trying to leverage the technology transfer process used in the IRC network to facilitate the match between technology demand and offer in OSS.

    A blueprint is a replicable and complete description of a set of tools and processes that satisfied a specific need. In this sense, a complete blueprint must contain the following items:

    • a complete description of the needs; this should include a complete textual
      .
    • description of what was requested, including mandatory and secondary requests
      .
    • a description of the context of the needs, for example within a public
      .
    • administration, with specific legal requirements, an SME, etc
      .
    • the set of technologies used
      .
    • the process implemented
      .
    • criticalities or additional constraints appeared during the implementation process
      .
    • an estimate of the human effort invested in the migration process.

    Why so much detail? Because replicability requires a significant amount on information not only on the technological means, but also on how those tools were used to create a complete solution.

    As these mapping efforts are already under way – for example the Italian Open Source Observatory has a listing section, called “vetrina” that provides short summaries of public administrations’ experience with open source – it may be interesting to propose a collaborative writing process, maybe wikipedia-based, to turn nice-to-know stories into replicable experiences.

    [tags] Open Source Observatory, OpenTTT, best practice [tags]

     
  • Roberto Galoppini 6:21 pm on May 17, 2007 Permalink | Reply  

    Italian Open Source Advocate: Carlo Piana 

    Carlo Piana is an Information Technology lawyer and a Free Software advocate, as Counsel to the Free Software Foundation Europe he advocates the adoption of free/open source software and interoperable systems by European Public Administrations.
    I asked Carlo, who I personally met about three years ago when we were both involved with the FSFE Italian chapter, to tell us more about his interest for free software and licensing issues.

    How did you get involved with Free Software?

    Well, that’s a long story. Here’s the short version. During late 90s I was using OS/2 as operating system of choice, but I did see no future for it, so I decided to switch to GNU/Linux as early as year 2000. It wasn’t easy, and some help was found in the local LUG. There I met Stefano Maffulli, Vice President of Free Software Foundation Europe.

    Then the Commission decided that Microsoft was abusing the market, and I was wondering whether the FSFE was somewhat involved. Stefano said something like:

    We are already an interested third party, now we need a lawyer with enough expertise to prepare our application with the Court. But time is really, really short.

    I thought it was just a couple of hours’ work, just to file the application, then I was supposed to hand over the matter to another lawyer, so I said:

    Well, I can help you with this initial step, then you will decide.

    It turned out to be slightly underestimated, as now we are turning the third year of litigation, and still do not see the end of the tunnel. So far I have invested thousands of hours in the case, and am still counting.

    In order to be effective in the case, I had to learn quick, and I became very interested also all aspects and implications of Free Software. I started helping people around with legal issues, and almost without realizing it, I was an active advocate. The media exposure of the Microsoft case was incredible, and perhaps this is the reason why people, including you, think I am important: because they know my name.

    Let’s talk about the Case now.

    Being involved in the Case somewhat changed my professional life, because I have never been in a litigation of that magnitude and importance. Even from a side seat, the pressure is enormous and ramifications are endless, the paperwork simply unmanageable. We now have gone through one interim case, and one merit case (we are awaiting the final decision), while one further appeal is on its way and we have applied also to that. The merit case was huge: thirteen judges, the hearing lasted five consecutive days, the “grand salle” was half packed just of lawyers and experts, the floor was barely enough for the two main parties, the rest was journalists, and it was not even enough. I said “side seat”, but don’t be mislead.

    Our role has been central in many occasions, thanks to the incredible work that those who back me have done. People of FSFE, but especially the members of the SambaTeam, have been incredible, these guys really rock! Jeremy Allison at the interim and Andrew Tridgell (Trdige) at the main case were outstanding and really, really credible, but also who worked behind the scene, like Volker Lendecke or another Italian, Simo Sorce, were incredibly helpful.

    But the case is way more than just that in court. The Commission is trying to firce Microsoft into compliance, after the first decision has not been suspended. But for the first time in history, there have been not just one, but two procedures for non compliance with the first decision: we are right now discussing the second one. The first ended by adding some hundred millions on the top of the at-the-time largest antitrust fine, somewhere short of half a million euro.

    Meanwhile, the Commission is cooking another case with a broader scope.
    While the first was on interoperability and lack of disclosure, as well as on the tying practice of bundling Windows Media Player with Windows XP, the second is about five different abuses in the server, client and application sector. In fact, interoperability is not just with network protocols, but also with the application layer protocols and formats.

    And the market has not been idle either: the ineffectiveness so far of the remedies has allowed the monopolist to double its share in the server operating system market, now well above 70%, the share in the client OS market has not lowered and many more fields have the windows logo on it.

    We are silently involved in that second investigation too. It not difficult to discover with whom because it is public on the Internet, but nobody still realized.

    What do you think is going to happen in the next future?

    The future is threefold. Free Software is gaining momentum by the day, over are the days when some people used to say that it was a toddler’s game. Most of the industry, from IBM to Google, from Sun to Oracle has various levels of engagement, and the mobile is the next frontier.

    Software as a service is probably the next step, which could shift the paradigm, but we are still far from maturity. In the middle lies the world of proprietary software and media companies, which will be eventually made irrelevant by the first two, but now they are fighting back with market power, DRM, software patents and the most dangerous weapon: people not realizing how much freedom they are losing any day.

    Antitrust is a good weapon to reestablish equanimity, but antitrust is also a political issue: just consider the number of monopolization cases in the USA in the last six years: 0. So we are at a turning point: public opinion must react now, and the first step is to convey more and more balanced information on these topic.

    Thank you Carlo, and please keep us updated!

    Technorati Tags: Free Software Foundation, Piana, Software Patent

     
  • Roberto Galoppini 11:33 pm on May 16, 2007 Permalink | Reply  

    Open Source Government: Italy launches its Forge 

    The Minister of Reform and Innovations in Public Administration, Luigi Nicolais, and the President of the Center for the application of Italian Ministry of Innovation and Technology Politics (CNIPA), Livio Zoffoli, today announced the latest initiative of the Italian Open Source Observatory.

    The Collaborative Development Environment (ASC, Ambiente di Sviluppo Cooperativo) offers Italian Public Administrations a medium to co-develop open source applications with other public administrations, market players and research institutes.

    Public Administrations need software aimed at addressing specific needs, and the collaboration platform has been designed to help them to involve partners in developing software public goods.

    Luigi Nicolais commented:

    Public Administrations will benefit of the advantages of open source software now, beyond software customizing they will learn how to share it easier, eventually opening a market for software services and reducing time-to-market and costs of acquisition.

    He also added that:

    Among e-Government’s strategic lines it is necessary to study and define a model to use open source software assuring economic sustainability, within a market where Public Administrations and software firms play their respective roles.

    About ASC

    ASC is a collaborative development environment based on GForge, to help public administrations to collaborate, using message forums , mailing lists and tools to create and control access to Source Code Management repositories.

    Related post:

    Italian Government: funds to sustain open source innovation

    Technorati Tags: Open Source Government, Italy, CNIPA

     
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