Recently, I got a chinese mini Wi-Fi camera, that was described as H.264 HD 1920×1080. I chose this model as it looked to be easy to mount (due to the form of a pin), independent (does not have to be near a PC or a network socket), mobile (can be easily moved to a different location) and small. It would be quite a good device (for its price), but it appeared to be too unstable. Also, it comes with an awful documentation and too little of information about its capabilities, even in Internet.
I expected to see the name of the manufacturer and the model on the package box or on the device itself, but was not able to do this. In other words, there was nothing, that identified the camera, except its form! Moreover, the package did not include even a document, that would explain, how to use it. However, the box had two QR codes – one for the iOS app and another one for the Android app. So, that’s how I was able to locate websites of (I assume) the embedded software developer (www.qr-cam.com) and (aslo assume) the manufacturer (www.ynkjdv.com). Eventually, the former helped me to find out the rest. By the way, the manufacturer declares its model as 811 WIFI, while the embedded software developer claims, that it (the “modal”, see below) is 601H. So, generally, it looks like the device has two brands and two models – YNKJDV 811 WIFI and Qr-Cam 601H.
The idea of bots is such popular due to the natural style of interaction. As it’s nice to be able to speak to a machine in a human-like manner (i.e., not through buttons and so on). And it’s also quite exciting to get the answer in a similar way (i.e., through speaking). For this reason we have Jabber bots, IRC bots, console bots (e.g., Emacs’ doctor), voice bots (e.g., Siri), and many more. Nevertheless, the concept of such bots is apparently incomplete as they can’t fully imitate the behavior of humans! In particular, the text messages just can’t express emotions (in a convenient way). To be able to do this bots would need bodies – e.g. eyes for users to look into, faces to express feelings, etc.
It’s absolutely common for a Redmine user to ask: How do I add custom HTML code to the Wiki content? Here by Wiki content users usually mean not just a Wiki page, as in Redmine a Wiki syntax enabled content is used everywhere (well, almost) – in project description, in issue description, in news, in comments, and so on. Anyway, normally, for Redmine such inquisitive persons get quick and definite answer: There is no way!..
As this is a common question, certainly, I used to ask it too. But, as I’m a Redmine plugin developer, I was able to “give” a different answer… Depending on the features, I developed, I used to implement some capabilities for embeding custom HTML code into different places of Redmine interface. There were no plan or design – I just implemented, what I thought at that moment can be reasonable and needful. Only after implementing those things I realized, that in several my plugins I implemented almost the same feature – the possibility to embed custom HTML code into the Wiki content. Luckily it was implemented in different ways…
To be more precise this was done in two my plugins – in Hooks Manager and in WikiNG. As some of these features are not foremost and, therefore, can be unnoticed and as the feature is commonly asked, I decided to describe its implementations in this article.
Github is the most popular online service for hosting and collaborative development of open source projects. And Redmine is the most popular personal and enterprise open source project hosting and management solution. So, no wonder, that these two systems are used together quite often.
Thus, Github’s Redmine service hook can be used to trigger fetching of repository updates by Redmine, when new commits are made to the Github repository. Unfortunately, it’s useless for the pure Redmine, as Redmine is not able to work with Github repositories directly (only through the local Git mirror, which needs to be created and updated manually)… Moreover, I am not aware of any solution, which could be used for this (even through the mirror).
Certainly, Redmine (especially its community) does much more to support Github. Thus, there is the plenty of tutorials describing how to mirror and keep Github repositories in sync for Redmine (e.g., this or this). Also there exist special plugins for making Github repositories easier usable under Redmine. The most noticeable such plugin is Github hook authored by Jakob Skjerning.
Presenting content in different languages is a needful and important feature. And most websites are using generally the same conceptual units for implementing it – translated “portals” of the site and a language switcher. But I believe, it’s a wrong concept!..
When you come to a Wikipedia page, how easy is for you to find your language in the language list? Even for English you need to check the huge list of languages, the majority of which you can’t read! WTF?..
Currently I work in Kayako – the company, that develops the most advanced and featureful help desk solution on the planet. So far I have worked on the KQL reporting engine and the REST API subsystem for the Kayako product. My personal (this) site runs on Redmine and WordPress and includes custom plugins and themes developed by me for these systems. So, I learned all these applications quite well! Thus, for Redmine I also authored the Mastering Redmine book, which was published by Packt Publishing.
Having worked in the IT outsourcing for more than 7 years I studied this industry very well and built a strong vision of it. Thus, I believe, that IT outsourcing has too many grave weaknesses, no one, usually, is trying to rectify. Moreover, these weaknesses do not seem to be known or recognized by any party – neither by vendors nor by customers. Therefore, in my (forthcoming) blog I aim to pay a special attention to them.
In this article we’ll discuss a blog post of a small outsourcing firm – not one of the best, but, most likely, one of the worst representatives of the IT outsourcing industry. But that’s even better as more serious companies are trying to detect and conceal their weaknesses, while companies like this one do not pay much attention to self-examination. Yet still, I believe, the problems revealed are common for all IT outsourcing companies!