lying on a bed or a couch half awake
half sleepy from last nights celebration
thinking in slow motion unsteadily
maybe i am getting too old for inebriation
still yesterday was a great day
we fought and celebrated a glorious win after long
hard work coupled with some luck
always leaves you humming a sweet song
i check my mails idly surf my social net
the net is quiet this morning
as if it too celebrated a lot last night
but check on it , it will be partying by evening
now tasks have to be done
daily chores yet to be begun
so we shake off the idleness like a shaggy dog who got wet
prepare to carpe diem ready get set
still an idle shrug and an occasional yawn
reminds aging bones to rest before dawn
On September 28th, 2010, The Document Foundation was announced. The last six months, it feels, have just passed within a short glimpse of time. Not only did we release three LibreOffice versions within three months, have created the LibreOffice-Box DVD image, and brought LibreOffice Portable on its way. We also have announced the LibreOffice Conference for October 2011 and have taken part in lots of events worldwide, with FOSDEM and CeBIT being the most prominent ones.
People follow us at Twitter, Identi.ca, XING, LinkedIn and a Facebook group and fan page, they discuss on our mailing lists with more than 6.000 subscriptions, collaborate in our wiki, get insight on our daily work in our blog, and post and blog themselves. From the very first day, openness, transparency and meritocracy have been shaping the framework we want to work in. Our discussions and decisions take place on a public mailing list, and regularly, we hold phone conferences for the Steering Committee and for the marketing teams, where everyone is invited to join. Our ideas and visions have made their way into our Next Decade Manifesto.
We have joined the Open Invention Network as well as the OpenDoc Society, and just last week have become an SPI-associated project, and we see a wide range of support from all over the world. Not only do Novell and Red Hat support our efforts with developers, but just recently, Canonical, creators of Ubuntu, joined as well. All major Linux distributions deliver LibreOffice with their operating systems, and more follow every day.
One of the most stunning contributions, that still leaves us speechless, is the support that we receive from the community. When we asked for 50,000 € capital stock for a German-based foundation, the community showed their support, appreciation and their power, and not only donated it in just eight days, but up to now has supported us with close to 100,000 €! Another one is that driven by our open, vendor neutral approach, combined with our easy hacks, we have included code contributions from over 150 entirely new developers to the project, alongside localisations from over 50 localizers. The community has developed itself better than we could ever dream of, and first meetings like the project’s weekend or the QA meeting of the Germanophone group are already being organized.
What we have seen now is just the beginning of something very big. The Document Foundation has a vision, and the creation of the foundation in Germany is about to happen soon. LibreOffice has been downloaded over 350,000 times within the first week, and we just counted more than 1,3 million downloads just from our download system — not counting packages directly delivered by Linux distributors, other download sites or DVDs included in magazines and newspapers — supported by 65 mirrors from all over the world, and millions already use and contribute to it worldwide. With our participation in the Google Summer of Code, we will engage more students and young developers to be part of our community. Our improved release schedule will ensure that new features and improvements will make their way to end-users soon, and for testers, we even provide daily builds.
We are so excited by what has been achieved over the last six months, and we are immensely grateful to all those who have supported the project in whatever ways they can. It is an honour to be working with you, to be part of one united community! The future as we are shaping it has just begun, and it will be bright and excellent.
delay deny obfuscate
remember all the promises you break
and all the love you fake
aint no piece of cake
even though the oaths you take
became lines in sand that you stake
cleaning the leaves of time you rake
much depends on the choices you make
going on anon till this rhythm i must break
sometimes you know when it is too much to take
mourning now in your personal life’s wake
you earned this trip to the melancholy lake
how much more how long till you break
down and confess your appearances are fake
you never anyone except your ego to partake
on your thirst for glory to slake
delay deny obfuscate
delude spin and permeate
love is good and addictive but so is hate
much depends on what all you rate
fear uncertainty doubt and cloud
are your companions most profound
is it just today or were
Well I have played with software (mostly but not exclusively) analytical, and I admire the zeal and energy of both open source and closed source practioners- all having relatively decent people executing strategies their investors or owners tell them to do (closed source) or motivated by their own self sense of cool-change the world-openness (open source)
What I dont get is people stealing open source code- repackaging without adding major contributions- claiming patent pending stuff- and basically making money by creating CLOSED source from the open source software-(as open source is yet to break the enterprise glass cieling)
you are either open source or you arent.
bi- sexuality is okay. bi-codability is not.
Next time you see someone stealing some community’s open source code- refer to this excellent link.
But, we cannot act on our own if we do not hold copyright. Thus, be sure to find out who the copyright holders of the software are before reporting a violation.
If you think you see a violation of the GNU GPL, LGPL, AGPL, or FDL, the first thing you should do is double-check the facts:
Does the distribution contain a copy of the License?
Does it clearly state which software is covered by the License? Does it say anything misleading, perhaps giving the impression that something is covered by the License when in fact it is not?
Is source code included in the distribution?
Is a written offer for source code included with a distribution of just binaries?
Is the available source code complete, or is it designed for linking in other non-free modules?
If there seems to be a real violation, the next thing you need to do is record the details carefully:
the precise name of the product
the name of the person or organization distributing it
email addresses, postal addresses and phone numbers for how to contact the distributor(s)
the exact name of the package whose license is violated
how the license was violated:
Is the copyright notice of the copyright holder included?
Is the source code completely missing?
Is there a written offer for source that’s incomplete in some way? This could happen if it provides a contact address or network URL that’s somehow incorrect.
Is there a copy of the license included in the distribution?
Is some of the source available, but not all? If so, what parts are missing?
The more of these details that you have, the easier it is for the copyright holder to pursue the matter.
Once you have collected the details, you should send a precise report to the copyright holder of the packages that are being misused. The copyright holder is the one who is legally authorized to take action to enforce the license.
If the copyright holder is the Free Software Foundation, please send the report to <license-violation@gnu.org>. It’s important that we be able to write back to you to get more information about the violation or product. So, if you use an anonymous remailer, please provide a return path of some sort. If you’d like to encrypt your correspondence, just send a brief mail saying so, and we’ll make appropriate arrangements.
Note that the GPL, and other copyleft licenses, are copyright licenses. This means that only the copyright holders are empowered to act against violations. The FSF acts on all GPL violations reported on FSF copyrighted code, and we offer assistance to any other copyright holder who wishes to do the same.
But, we cannot act on our own if we do not hold copyright. Thus, be sure to find out who the copyright holders of the software are before reporting a violation.
When performing the exercise, subjects are given a list of 56 adjectives and picks five or six that they feel describe their own personality. Peers of the subject are then given the same list, and each picks five or six adjectives that describe the subject. These adjectives are then mapped onto a grid
A Johari window consists of the following 56 adjectives used as possible descriptions of the participant. In alphabetical order they are:
When performing the exercise, subjects are given a list of 56 adjectives and picks five or six that they feel describe their own personality. Peers of the subject are then given the same list, and each picks five or six adjectives that describe the subject. These adjectives are then mapped onto a grid
A Johari window consists of the following 56 adjectives used as possible descriptions of the participant. In alphabetical order they are:
DECISION STATS 