[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse.org-architecture-council] Using Google (or generally external) features in Wiki and for organization.
- From: David M Williams <david_williams@xxxxxxxxxx>
- Date: Sat, 1 Nov 2008 23:41:12 -0400
- Delivered-to: email@example.com
I think this issue of what's in Eclipse IT vs. others (and thus under
calendaring systems, but know it also applies to blogs and other such
"public" means of communication. And I know I should pay more attention to
But for now I simply wanted to cross-reference this line of discussion
with a recent bugzilla entry,
Contrary to it's title, it has to do with whether or not we need an
Eclipse sourced blogging system ... which seems similar to the issue of
whether we need an Eclipse sourced calendaring system ... and probably
even more important, since it's pretty clear that "important information"
could be contained in a blog entry.
I'm just posting here to make sure bug 247882 get's proper exposure and
discussion by those who care and understand such issues.
August Georg Schmidt <g.schmidt@xxxxxxx>
10/09/2008 04:35 PM
[eclipse.org-architecture-council] Using Google (or generally external)
features in Wiki and for organization.
today in the AC meeting we have had a request for using Google calendar
for managing the meeting and the attendees.
Generally the usage of such tools has several drawbacks from my point of
1. We add structured information to Google, when we are doing
They are moving strongly into our life and they are extreme collecting our
data and behavior in the web. I dislike that point. With this information
a lot of wrong things could be made.
2. The search in our WIKI is negatively affected.
You are not able to search on this type of content? e.g. an example is the
calendar on the AC page.
I don?t want to add further work to ones task. And I do not have an idea
yet, how to reduce the amount of time that has to be invested without such
a tool for coordination.
Therefore I would vote with 0 on such a point.
Generally I would add a comment of moving this information out of our
As we move more and more information out of our IT system the usage of
search or similar features is getting more and more complex on our data.
As a result the only chance to get access to the content is the use of a
spider to crawl the website. This crawler would be used for creating a
search index or similar. If we want to improve access to information in
our IT systems ? like wiki or other page content ? we should be in control
of our data. If not, accessing the real content we would always have the
issue on making a decision, what is real and what is just navigational (or
similar) data. Access to the content is therefore much more complex and
that could affect the abilities of search algorithms.
Search or other knowledge management features? as categorization, content
based routing, search and many more will get more and more complex or may
work not optimal.
>From my point of view we should keep control on such data. This would give
us options for flexible operations with our content.
eclipse.org-architecture-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation. To be permanently removed from this list, you
must contact emo@xxxxxxxxxxx to request removal.