Thanks go to Michael C. Harris who noted this now accomplished wishlist in that 2008 post.
"I'd like to be able to use Habari as a lightweight CMS for clients. The most important features missing for that are page hierarchies and a permissions system. Multisite and multi-author support would be great too." Sure, the technical features will change over time but so can the blurb. Build the bike shed right away, but just plan to paint it every few years. On Saturday, April 6, 2013 12:15:03 PM UTC-4, Les Henderson wrote: > > I agree with you about mission statements in general. Corporate fluff for > the most part. Read once when hired and then only seen in annual reports. > Perhaps try to think of it more as a philosophy, an elevator pitch or a > marketing blurb, all of which, including a mission statement, are things > that you've been trying to come up with year after year without consensus > or progress. > > It was actually your suggestions in this post, > https://groups.google.com/forum/?fromgroups=#!msg/habari-dev/rzyMnWyItYA/RA3Ql9cjSEMJalong > with input from others, that motivated me to give it a go. > > Just as programming code is never perfect, the same holds true for > marketing code. What I see this as, more than anything, is a way for people > to find the project, quickly assess whether it is something they are > looking for (in under a minute) and perhaps even motivate them to > contribute or give it a try. An SEO bumper sticker if you will. > > People don't search for spiritual goals in Google. They are looking for an > "ASL open source blog project", "lean CMS dev kit for multisite blogging" > "multilingual multiple author blog platform". Or, at least if they were, > they would not currently find Habari. > > The real question is, if you saw this as the blurb for some other > competing product that you had never heard of, would you be intrigued > enough to investigate further. > > > On Friday, April 5, 2013 9:51:57 PM UTC-4, Chris Meller wrote: >> >> I'm not sure what the purpose of this was, really, but for a mission >> statement it's very wordy. It's a single long sentence that tries to cram a >> lot of unrelated and technical things together. >> >> Perhaps "mission statement" was a misnomer. A mission statement should be >> short and to the point (I'd say half this length, at most). If it wouldn't >> be readable on a single PowerPoint slide from the back of the room, it's >> probably trying to cover too much. It should cover the spiritual goals of >> the project, not necessarily the technical ones. Technical requirements >> change and fade in and out of importance; the community-driven nature is >> the key point. >> >> But like I said, I'm not sure what the purpose of this was. I'm also not >> big on mission statements in general, they tend to come off pointless and >> corny to me, so that's just my 2 cents worth. >> >> >> On Fri, Apr 5, 2013 at 9:21 PM, <[email protected]> wrote: >> >>> As take-up accelerates this kind of thing will become very important in >>> order to keep the spirit of Habari alive ... I like it. >>> >>> >>> On Friday, 5 April 2013 21:36:50 UTC+1, Les Henderson wrote: >>>> >>>> First let me say that this was developed based on your own suggestions >>>> over the years along with some current ones from people you know and >>>> respect. >>>> >>>> I've juggled it around for hours, but am still hoping for your views in >>>> the hopes it can be polished further and officially established as the >>>> current mission statement, unless something better is presented. >>>> >>>> *The mission of the community-driven Habari Project is to continually >>>> improve upon a lean, modular, highly customizable, ASL licensed >>>> open-source >>>> PHP blogging engine featuring multilingual, multi-site and multi-author >>>> permissions support using well-documented development protocols and the >>>> latest technologies to satisfy the evolving needs of professional CMS >>>> developers.* >>>> >>> -- >>> -- >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/habari-users >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "habari-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-users --- You received this message because you are subscribed to the Google Groups "habari-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
