Difference between revisions of "Information Sharing/Meetings"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Minutes by Stefan)
Line 134: Line 134:
  
  
[[Category:Information Sharing]]
 
 
[[Category:Website]]
 
[[Category:Website]]
 
[[Category:Minutes]]
 
[[Category:Minutes]]

Revision as of 09:31, 5 September 2007

6-Sep-2007

1 pm - 2 pm

Agenda

9-Aug-2007

1-Aug-2007

Minutes by Matthias

so-doc analysis

Martin prepared an analysis of all files of so-doc by age/type/team

The vast majority of files is stone-age old. It also seems that we use so-doc more like a team server rather than a document server (whatever the difference is).

How can we find the nuggets, alas, the valid information that should better be hosted somewhere on ooo? The age is just an indicator. It is no sufficient heuristic to decide on the fate of the files.

defects

defect category

We identified a fifth defect category: redundant information (between ooo.org and ooo-wiki)

Example
Someone hosts information on his ooo project site and on the ooo-wiki because the wiki does not offer the same left navbar as the ooo project sites do.

The five defect categories are:

  1. total absence of necessary information
  2. outdated information
  3. up-to-date but not open accessible information
  4. redundant information
  5. ( outdated and not open accessible information )

How to record defects (->measure of success)

1) IssueTracker is an option.

Information defects (according to the 5 defect categories) are submitted to IssueTracker.
The OOo Team Leads will be the default owner for such issues.
Pros: official, trackable, manageable

Stefan will present the idea in Michael's staff meeting.

2) assign a category to pages that need attention

Examples
for so-wiki: Template:MoveToOOo
for ooo-wiki: http://wiki.services.openoffice.org/wiki/Category:Candidates_for_speedy_deletion

MediaWiki extensions

Are there any extensions to MediaWiki which could help to do a better job?

AI for all
Matthias: how do the flags work on Wikipedia? -- ("This article needs your attention")
Martin: web tracking for MediaWiki, generate automatic site structure for MediaWiki sites?
Stefan: utilize Omniture Sitecatalyst to identify non frequented pages

Search

Unified Search for all ooo

Goal is to eliminate redundancies in favor to reduce search match doublets

Martin suggests to use Google over custom search engines for each oo site.

Search Engine Optimization (SEO)

Which search terms in Google lead to what pages on ooo? What search terms are used most often? We can have a look into SEO.

  • PageRank for our entry pages
  • use of keywords
  • proper use of HTML (also goot for accessibility)

Omniture Sitecatalyst to identify non frequented pages (consolidation)

Omniture can track the frequency of page visits for ooo. This data should be used to inform the project leads and to reveal insights on how to improve the project sites and to identify opportunities to combine distributed information.

ooo sitemap

Matthias has started to create a Information Architecture (IA) -oriented site map:

Initial findings

  • the header is different for home and project pages: the search function is top right, respectively integrated into the leftnav
  • the home page has no user account feature
  • the left navbar is optional, ie. some projects have removed this area
    • esp. Support has no left navbar, which offers Search, Sitemap, FAQ, Get Help?
  • logout leads to the login/register page. By doing this it changes the context entirely.
  • <ironic> do not visit the support page if you need support </ironic> It is a textual mess.

27-Jul-2007 kick-off

Minutes by Stefan

What leads to this project

  • problems occurred with new contributors (CH2000) who didn't find the info they needed, asking the developers and got a pointer to outdated info, asking about outdated info - the developer agrees - end of story

Michael Bemmer was involved in this incident and researched himself a bit in our information infrastructure. Doing this he got aware of the following facts: Our informational infrastructure is way too complex to be able to acquire helpful information easily. Many documents and sites are outdated, some not accessible to the whole community because posted on Sun internal media, or simply not existent.

Michael Bemmer champions this project and expect a list of "where to post what" recommendations as one of the outcomes of this project. He further expects the evaluation of internal information infrastructure (e.g.so-doc) wrt. outdated,"old", information pieces and wrt. the question if we could probably get rid of some medias in favor of less ambiguity

Why the SMEs (MH,MMP)

MH as the technical OOo guy and generalist for all kind of issues around community related issues, and MMP as highly skilled communication and UX "scientist" seem to be the perfect team for the job.

Both agreed on the charter so far, but all the three team members are aware of the fact that minor adaption to the charter may still be necessary. The team also agreed on the schedule of a weekly meeting, 12 times from now on which means immediate action.

The team talked about the following further topics:

  • necessity of a rule of separation between information and communication, which I currently break with this mail :))
  • Ownership
    • project page maintenance
    • doorman to guide new developers
    • active acquisition
    • address website problems
  • information transfer internal -> external
  • information restructure (site)
  • presentation about communication and the responsibility of the sender

Further things I would like to mention/discuss with the Team:

As far as I see we got 4 classes of defects

  1. total absence of necessary information
  2. outdated information
  3. up-to-date but not open accessible information
  4. ( outdated and not open accessible information )

As we are not doing a Sigma Project we should start to proceed the "just-do-it" kinda things What are these? Actually as soon as you discover one of the former categorized defects take care that it'll be addressed and log it.

example
When you hit an outdated page, record it in a list and take immediate action like contact the owner to fix it.


We were all not too happy with the goal statement what about this here?

Possible adjusted goal statement:

Improve the ability of community participants to access relevant information

Documents

  1. Information Sharing by Stefan
  2. OOo Website User Groups by Matthias
Personal tools
https://wiki.openoffice.org/w/index.php?title=Information_Sharing/Meetings&diff=prev&oldid=44842
wiki.openoffice.org
crawl=CC-MAIN-2020-10
30809
application/http; msgtype=response
sha1:WDPHDG2UK6Y7P2AW2KZNHLDC5EYUDMVK
<urn:uuid:f23f8256-f65d-40ef-8725-61dc12f44750>
2020-02-23T08:07:44Z
34.207.3.4
text/html
sha1:YAWXGUT6Q3NJVIKPMO2DOHO75OMP7WBS
<urn:uuid:82e96a9a-d3ad-4045-a38a-3c454601fb89>
https://wiki.openoffice.org/w/index.php?title=Information_Sharing/Meetings&diff=prev&oldid=44842
response
<urn:uuid:1ec584b7-6b81-4511-b6d8-2a3efe95193d>
isPartOf: CC-MAIN-2020-10
publisher: Common Crawl
description: Wide crawl of the web for February 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-136.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/