Each time a mail is sent to many lists at the same time, even from
registered users, the mail is stopped and requires approval from the
admin of the list.
Is there a way to fix this ?
Admin of this list...
> Yes, I was thinking of the Wikimedia Foundation's projects. Would
> Wise-Nano or Nanopedia (the hoped-for end product) be a good addition to
> that group of projects?
> If my site uses a Creative Commons Attribution-Share Alike license, does
> that fulfill the Gnu license, or do I have to include Gnu boilerplate on
> any text I copy from a Gnu'd site?
1) The appropriate list to discuss whether a particular project can be
part of the Wikimedia set of projects is
I've therefore CC'd my response there.
2) Generally, Wikimedia projects are very broad. There is only one notable
exception to that rule, the recently created Wikispecies (which is why I
think it should be incorporated into a larger Wikidata project).
It has been proposed in the past to have a "Wikipolicy" project as a sort
of open brainstorming space for determining useful political policies on
various issues. That might be an idea worth developing further, but I
would oppose a narrow project like Wise-Nano.
3) All text-centric projects are under the GNU FDL (Wikispecies licensing
is not decided yet), so that would have to be the license to use.
I made some experiment on fr, and integrated the goings-on in the
community page. You can have a first look here :
The idea is that the community page hosts the ongoing information (at
least the most recent one). A link allow to easily go to history.
The edition follow a timeline. Most recent on top. The beginning of the
line, in bold, indicate roughly the type of topic (Foundation, Tech, New
project, Publishing etc...).
Of course, on meta, the community page is ... the main page.
So, roughly, on one side, we would have the ongoing information, on the
other side, the permanent references.
Add a pinch of rework on the various "current events", "news" and other
announcements, plus a big spoon of translation...
What do you think ?
There are a lot of domain names for all the Wikimedia projects. Some are the
property of Wikimedia, some of friends of Wikimedia.
I have the impression that the dealing of requests regarding domains is done ad
hoc by diffrent people.
To make sure that the overview is not lost, the usernames and passwords for
those domains, it is not forgotten to renew domains, to be a contact person for
friends of Wikimedia who are willing to transfer a domain and for requests for
buying new domains, it would be good if there where one person responsible.
Wikidata is a proposed wiki-like database for various types of content.
This project requires significant changes to the software (or possibly a
completely new software) but has the potential to centrally store and
manage data from all Wikimedia projects, and to radically expand the range
of content that can be built using wiki principles.
Imagine that you can edit the content of an infobox on Wikipedia (e.g. the
country box for Germany) with one click, that you get an edit form
specific to the infobox you are editing, and that other Wikipedias
automatically and immediately use the same content (unless it is local and
needs to be translated).
Imagine that some data in an article can be automatically updated in the
background, without any work from you - whether it is the development of a
company stock, or the number of lines of code in an open source project.
Imagine that you can easily search wiki-databases on a variety of
subjects, without knowing anything about wikis.
This project is separate from the Wikimedia Commons, because a Wikidata
database does not necessarily have to be useful for another Wikimedia
project, and because it is larger in scope.
Astronomy - '''space.wikidata.org''' (spc.wikidata.org)
* astronomical objects
* observatories and telescopes
* space missions
Society - '''society.wikidata.org'''
* Schools and universities
* Cities, Countries, Subdivisions
* Ethnic groups
* Radio and television stations
<end excerpt, more examples on Meta>
Jimmy has just registered wikidata.org. We both agree that such a project
makes sense. I've had similar ideas before, but the (IMHO premature)
existence of Wikispecies has compelled me to put some of this down and
develop the idea further.
There's a GUI mock-up on the meta page of what data entry could look like,
and there's a (very rough) proposed implementation strategy. If someone is
willing to do so, it may make sense to create a proof-of-concept from
I'm putting this idea out there for now so that it can be picked up at any
later time. This is not urgent in any way, but it could open up a huge new
range of projects where Wikimedia can compete with proprietary content
producers. (Oh, and corporate users of MediaWiki would love us for this.)
I see two immediate consequences for us:
1) I believe that, if we do a database redesign, the needs of a project
like Wikidata should be considered; that is, we should come up with an
abstract scheme that allows storage and revision-handling for many
different data structures. Otherwise we'll have to do another huge
2) For Wikispecies, I suggest that those involved with the project make
sure that all data entered into the wiki is in a *structured form* so
that it can then later be easily converted into a real database
I have been trying to think about the past days issues.
Fuzheado and others mentionned the goings-on as the place they go to when they want to be kept updated.
I was glad to hear that, because I had the feeling this page was not very much used. If it is, then it is worth :-)
I'll revive a discussion we had with Erik and Mav on this goings-on issue, related to the "news" issue.
The "news" is the place where we keep track of relevant events in a chronological manner. Typically, we find news such as
- xx.wikipedia reached 10000 articles
- zz.wiktionary switched to utf today
- there was a meeting in city tt today
- we received the prize pp
- download time planned today
Currently, these news are very short (not detailed) with links. The audience is "contributors" and "people outside the project".
The display is actually a sort of a weblog.
Basically, it is not translated, but it is usually written in simple english.
The "goings-on" is the place where we mention events or discussions. This is a lot "internal kitchen" which imho is none of the business of external readers.
The information is first sorted by "type", then a little bit by "date".
We had hoped that the information would be translated on local goings-on, but it is just not done, even on big wikipedias such as the english one.
There is no easy navigation between languages.
The information is not as short as on the "news". Often, a short summary explains the issue itself. It is not always written in simple english.
Do you think the "news" and the "goings-on" should merged ? Or that one should be made the subset of the other ?
How do we manage the overlap of information ?
It seems to me that the current goings-on subsections are a bit confusing. I often hesitate between 2 sections when I want to add an information.
Should we keep the "by topic" classification ? Or switch to another type of classification ? If we do keep "by topic", should we keep the current classification or is there a better proposal ?
Should we try to identify timeline better ? Either by organising goings-on according to "date of addition" or introducing more date references in the "by topic" sections ?
How could we advertise goings-on better so that people not only think of reading it, but also to update it ? I think it is very important that we do not have to write dozen of times the same information in several places. This is a total loss of time and energy.
Translation is basically non existent. We have three options
1) We do not even try to translate and we try to keep to simple english -> It think this is not a good move
2) We have an english version on meta, and translations on local project -> We tried that for 6 months, obviously it does not work
3) We have all translations on meta -> Translation requests page on meta seems to be working quite well now. What would you think of trying goings-on translation and giving up local translation entirely ?
If translations are done on meta, how could we better advertise meta goings-on on each local project ? How to tell those new ones that there is another life beside local project and that they are welcome to join ? Links in welcome messages ? Improvement in the recent changes editorial sections ? Promoting adding links in local pumps ? In news ? Adding a link in the menu bar ?
All this would be much easier if meta was more multilingual, with language preference for menu, and easier navigation between languages (rather than awkard templates). There were discussions about doing this in the software ? Is there any news of this ? Is someone interested in doing it ? If so, when can we have hope ?
Errrr... what would motivate the developper to do so ?
Who can help improving all this ?
May I have chocolate ice-cream on top ?
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!