- The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
The result was delete. joe deckertalk to me 18:50, 25 April 2011 (UTC)[reply]
- HWIOS (edit | talk | history | protect | delete | links | watch | logs | views) – (View log)
- (Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)
A software project that is under development. No indication of the software being in active use; no significant coverage in reliable secondary sources. --Demiurge1000 (talk) 12:49, 18 April 2011 (UTC)[reply]
- Note: This debate has been included in the list of Software-related deletion discussions.
- Delete. Yet more "customer relations management" software (aiming to make CMS software behave more like regular networking applications.). This one contains a "vision" heading containg promotional language that discusses what they eventually hope to achieve: The mid-term focus of HWIOS is to refactor the software to stable production-quality, and to allow a module ecosystem to thrive. HWIOS aspires to be a next-generation CMS for e-learning and e-work, by allowing presence-aware web-applications to be developed in a flexible and clean web-framework. E-learning and e-work include sharing of knowledge based on documents, drawings, voice and video, as well as experience-based learning methods found in virtual environments. - Smerdis of Tlön - killing the human spirit since 2003! 15:32, 18 April 2011 (UTC)[reply]
- Delete When the article BEGINS by telling you who is financing it, it makes it difficult to read the rest....but it is still not notable. Dennis Brown (talk) 18:43, 18 April 2011 (UTC)[reply]
- Delete Per the above. The creator of the article is only involved in this article. Seems to be promoting a product. Zlqq2144(Talk Contribs) 14:10, 19 April 2011 (UTC)[reply]
- Public interest, but insignificant (yet). This was my first wikipedia article ever, so please forgive me the initial pitfalls. I removed/replaced all text that could be interpreted as promotional/sponsor orientated. The R&D project itself is BSD-licensed on Contributors copyright and open source for the public, so it could be of potential interest to the public, and is not driven solely by personal/commercial interests. Instead of narrowing or deleting the already exotic subject, i could make a 'Websocket CMS' article, describing the technique of applying websockets to CMS design. The HWIOS article could then be used as reference material, because it's the first and only known websocket CMS atm afaik. — Preceding unsignedcomment added by Phrearch (talk • contribs) 09:56, 20 April 2011 (UTC)[reply]
- Let's look at the references.
- 1st one [1] does not talk about HWIOS.
- 2nd one [2] not RS. Seems to be a website with updates from the creator of jinfinote, which is not notable itself.
- 3rd one [3] seems to be created by Phrearch, that's SPS. Ignoring that, it's not RS.
- 4th one [4] does not mention HWIOS
- Since, apparantly, Phrearch is involved in this project, this may be considered as promotional? Zlqq2144(Talk Contribs) 10:17, 20 April 2011 (UTC)[reply]
- Also, you said yourself that it's 'insignificant'. The 'yet' part does not matter, since wikipedia is not a crystalball. Similarly, 'potential interest' does not grant notability. Also, I advise you to read the general notability guidelines. Zlqq2144(Talk Contribs) 10:20, 20 April 2011 (UTC)[reply]
- Delete Too much of this promotional stuff coming in - bin it Brookie :) - he's in the building somewhere! (Whisper...) 10:50, 20 April 2011 (UTC)[reply]
- Delete Agreed. I'll stick to the usual blogs instead :) I haven't read anything about the websocket CMS suggestion though. This is imo notable enough, since it changes basically every aspect of today's cms software(from http-based to persistant websocket connections). I'll be happy to start an article about that, or does that need to be mainstream info as well? Currently there are no references on the websocket cms subject on the net, except from this particular project. I know it has somewhat of a crystalball feel to it because of that, but this is what the article about websocket CMS would be useful for; to describe the benefits from moving from http to websockets in general. The HWIOS project is just the first example of applying this html5 technique to CMS software, and therefor has at least some significance in that perspective imo. — Preceding unsigned comment added by Phrearch (talk • contribs) 11:56, 20 April 2011 (UTC)[reply]
- That needs 'mainstream' info as well. All wikipedia articles do. 'Currently there are no references on the websocket cms subject on the net, except from this particular project.' There you go. If it's true (I haven't checked), then it fails WP:N. Saying it will be notable in the future is the exact definition of WP:CRYSTALBALL. Come back when it is notable. However, we do seem to have a CMS article, though I am not knowledgable in that subject so I don't know if it is what you want. Content management system. Zlqq2144(Talk Contribs) 12:12, 20 April 2011 (UTC)[reply]
- Agree with Zlqq2144 - I fear you would be wasting your time creating a Wikipedia article about websocket CMS, because that too would not be notable. One slight caveat with Zlqq2144's comments is that just because there are no references on the net doesn't mean something's not notable - if there are reliable published sources that are dead trees then that's just fine for notability. However, of course for software under development, lack of net coverage means there's probably no offline coverage either. --Demiurge1000 (talk) 14:38, 20 April 2011 (UTC)[reply]
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.