Jun 7, 2014

Installing emacs24 on Debian wheezy , the proper way

A  google search for wheezy emacs24 gives various blogs, almost all of which end up with 'make install' rather than 'dpkg -i ....deb' .
Here is some simple steps to make a deb package of emacs24 for any debian version. The constraint is that we don't want to needlessly upgrade the rest of wheezy.

Getting the required files
First, get the source files.  From the emacs24 package page, download the source packages. The spec file is not really needed. Get the emacs24_*.orig.tar.bz2 and emacs24_*.debian.tar.xz
(I'm not providing the link to the files as they will soon go out of date )


Unpacking the files

The good old 'tar' can extract both the files.

tar jxvf emacs24_*.orig.tar.bz2
cd emacs24_*.orig
tar Jxvf ../emacs24_*.debian.tar.xz 

Note the 'J' option to tar to extract the 'xz' file, and 'j' to extract the bz2 file.

Installing the dependencies

We are going to use the 'debuild' wrapper. 

sudo apt-get install devscripts

Also, look at the debian/control for Build-Depends: line, and make sure
they are installed.  One can use the command dpkg-checkbuilddeps for checking this.

One thing I noticed that libgnutls28-dev is not available in wheezy, so change it libgnutls-dev, which is available in wheezy.

Do the build

This is really a single command 'debuild' and a wait.

debuild

After some time, there should be several deb files in the directory above.
cd ..
ls -1 *deb
emacs24-lucid_24.3+1-4_amd64.deb
emacs24-lucid-dbg_24.3+1-4_amd64.deb
emacs24-nox_24.3+1-4_amd64.deb
emacs24-nox-dbg_24.3+1-4_amd64.deb
emacs24_24.3+1-4_amd64.deb
emacs24-dbg_24.3+1-4_amd64.deb
emacs24-bin-common_24.3+1-4_amd64.deb
emacs24-common_24.3+1-4_all.deb
emacs24-el_24.3+1-4_all.deb

The installation

There are multiple tools like debi/gdebi etc. but this is what you essentially need to do:

sudo apt-get install emacsen-common
sudo dpkg -i emacs24_24*deb emacs24-common*deb \
emacs24-bin-common*deb

You may want to purge existing emacs23 from the system before installing emacs24

The drumrolls 

emacs -version

And finally

a request ... never ever ever do a 'make install' as root on your debian. There is always a way to make a deb, which can be later uninstalled cleanly.
 

Oct 21, 2013

biz idea : crowd sourced education site

This continues on my MOOC vs Crowdsourced theme. The problem I'm trying to fix is that MOOC is still like a 'hill top' institution, where a group of people decide on the content, and there is no evolution by genetic mutation, and it's very much like the closed source software industry. In this scheme  content does not improve like wikipedia.

And most of the people want certification more than education, so the hill top institutions backed MOOC's will continue have a strong customer base, as long as certification will be backed by the institution. On the other hand, a crowd source site ( like wikipedia) will have no certification, authenticity, but will have better quality of content and overall learning.

In my opinion, what is needed is a github for nano-sized self study modules, where anyone can fork, patch and provide a pull request and the content is continuously updated. Also, the packaging of  nano sized self study units into a course, very much like the linux distribution packaging, will be needed. So things like CBSE - Physics - XII can be created out of several self study modules, which have been authored and improved by people world over, and in possibly their native languages.

This bring out another feature of MOOC's ... complete reliance on videos and/or audio, and that these non-textual media are incompatible with the my scheme.  In my opinion, videos were merely the first step, taking out best teachers and broadcasting them to the world. However, it's non trivial to improve these content once they are recorded.  I'ld argue that current generation of online education is still extending the old school thought on to the new medium of internet, rather than redesigning learning for the masses, by the masses.

Now the technology and processing power have reached the level, where it's possible to provide a personalized online environment suited for each individual, for a huge internet population, and let the population improve the content. This platform will be a massive convergence of the best in text to speech, automatic language translations, animations, and possibly more technologies.

There are couple of business models which an be around this. All the crowd generated content has to be freely accessible. The software that drives all this may or may not be open sourced, but the data formats for the content have to be open royalty free applications. Revenue generation is possible by charging for premium courses ( dedicated courses for  certification courses).


This post has gone too long already  , will probably spill the beans in next entry.

Keep learning,

biz idea : excel to app ( desktop / mobile / web )

From 1920's to  1960's in US  , in the age of manual telephone exchanges, the job market for 'switchboard operators' was booming. Some famous editorial remarked that it looks like everyone in US will eventually become a switch board operators. And soon , it was proven true, imagine .. we actually have to dial the number we want call !!

Something very similar has been happening to the programming. The fact is, that today  Microsoft Excel is perhaps the easiest to use functional programming platform. People have built a great variety of data systems using Excel.

This post is about a thought process of creating a service where use can upload a  Excel file, and download desktop/web/mobile app for that. Let Excel be the IDE  (-: 
Let me call this service  ExcelAsIDE ( EAI) for the time being...

Flow

The App should be doing a true render of the formatting , formula, charts etc, including the dynamic data sources.
As easy as it can be. Just upload the xlsx file. Configure the data sources if any. Decide how the outputs cells / charts will show up on the screen. And download / run the app in the next screen. It should be possible to generate apps for all screens , cpu's and OS's

Technology

Hmm.. the more interesting stuff . Perhaps the biggest stuff this will require is a VBA compiler, and an implementation of complete Excel API. I'm sure there is some Microsoft licensing stuff here, which will have to be worked out.
The good thing is that all the information is available and open. Office Open XML file format , Excel API, VBA .. everything is available.




Oct 18, 2013

biz idea : come-in .. secure screen sharing site.

For Windows world, we have several screen sharing and remote controlling services, like team viewer, google hangout screen sharing, copilot etc. However, no such service exists for the Unix family. The good thing is, that all client side software is already present on the desktop, and this a pure server software requirements.

This service is being called come-in for this document.

Use cases

The first use case is, to allow a remote friend to login in the machine and do some stuff. The remote friend can use screen / tmux / vnc to share screen with local person, or just some magic command and exit.
 The 'Needy' is the person requiring assistance, and 'Friend' is the one who will will remotely login to help out. 
  1. Needy pings Friend on IM or in any other way. 
  2. Friend shares his public key with Needy. 
  3. Needy runs the come-in client, and enters Friend's public key. 
  4. Friend runs come-in client and invokes 'Connect'
  5. Friend is logged on to Needy's machine.
A instant 1:1 session should be possible without creating site login. The Friend's public key will be stored by come-in client, so needs to be entered only once.

Another use case is remote access of several machines by a group of person. These will use site  logins and registrations of machines. The server data stored will be only for lookup of group of machines to group of people.

Security considerations

The closed sourced software and services work  on the assumption that their servers are impenetrable. And moreover they want users data in plain text on there servers for some evil reasons.
Now as we are not evil, we wouldn't want to have any user data in plain text on our servers. We work on assumption that our servers and storage is vulnerable1, and even in that case, user's machine connected to server should be safe and secure. 

Architecture

The come-in client is wrapper over ssh client. Several ports will be setup as  forward / reverse proxy.  Some of these ports will be client to client, where as some may be client to server. The client to server connection is only used for identification. It should be noted that even if the server is malicious, it'll not be able to fool the client into connecting to a non-desired client, because the client to client connection, the data connection, is seprate from this client to server connection, and is encrypted end to end.

The come-in server needs to have extra functionality, of a 'matcher' and of a 'proxy'. It's possible the come-in server is an especially patched ssh server, or just a configuration of ssh server along with separate proxy and matcher program.

The come-in client will be able to wrap screen/tmux/vnc to provide a finished product feeling

Business Angle

The wise folks have told us that the value is discovered by customers, so I don't want to go in there.

The development of basic ssh sharing is about 100 hours of work. Server deployment can be taken as another 50$ per month.

This can work on a freemium model. The 1:1 can be free for upto 1 hour or so. The persistent connection model can be paid for something like 1$ per machine and 1$ per user per month.  This will also require to implement MIS like stuff, and some more fanciness which is another 100 hours of work.


So, it should be possible to bring up this service in 1 month flat.


Game for it ?

Oct 16, 2013

git flow for NVDA India branch


[ Note: This information is moving to http://code.google.com/p/saksham-projects/wiki/InNvdaSource ]


NVDA is a open source screen reader for Windows. There is a project underway right now for making sure the feature set required for Indians are contributed to it. This post is an attempt to describe the process and tools.

Flow

NVDA has it's own git repository. The 'master' branch is always ready for release, and all the work happens on the per-ticket branch, which are based on master. The  incubation branch is called 'next', on which the ticket-branches linger for testing.

For their work, India team has a repository in bitbucket. This repo completely mirrors the official NVDA repository. It also contains the per-ticket branch that India team members are working on. Finally, it also has the 'in_next' branch, which contains only the work being done by India team members.

When India team members are satisfied with the code in a particular branch, they will update the ticket with the branch / repo information, and also drop mail to nvda-dev mailing list about the feature. From then on,
NVDA maintainers can start their process of incubation in next and then moving in the master for release.

This flow requires the work to be kept 'live' in two branches, the feature branch, as well as the in_next branch. Every few weeks, it's required to merge master into the ticket-branch, and merge ticket-branch into the in_next.

Details

This section lists describes the conventions and git commands
NVDA has the convention of naming branch  as  't1234' for the ticket #1234.
There is another thought process, that branches should be named like 'in_t1234', so that they are different than the one that NVDA team uses.
This will help India  team member identify each other's work.
So any branch that exists in NVDA-India repository, but not in NVDA repository has a 'in_' prefix, and the same purpose as corresponding NVDA repository

Setting up the Repo 

In a empty directory, run following commands:
git init
git remote add nvda git://git.nvaccess.org/nvda.git
git remote add ours git@bitbucket.org:manish_agrawal/nvda.git
git fetch --all
git pull nvda -u master
git pull ours -u in_next
At this point , open readme.txt to see how to compile NVDA.

Starting on a ticket branch

git checkout master  
git pull
git checkout -b in_t1234
git push ours -u in_t1234

Updating work to in_next

git checkout master
git pull
git checkout in_t1234
git merge master
git commit -a
git push
git checkout in_next
git merge master
git merge in_t1234
git push

These instructions and background should be sufficient for someone to get started in contributing to NVDA via the NVDA-India repository.

Some handy git commands

To see exact diff between two branches, use branch1 dot dot branch2

git diff master..t1234
git diff master..
git diff master...t1234
git diff master...

To move back a branch from 'next' to 'master' , we'll have to use the old diff-patch mechanism


# Get the old branch
git checkout t1234
# bring it up to date, replace nvda by the name of nvda remote
git merge remotes/nvda/next
# save the differences
git diff remotes/nvda/next... > patch.1234

# switch to master
git checkout master
# create new branch
git checkout -b in_t1234
# apply the patch
patch < patch.1234
# review
git diff
# commit, push etc..  


List of tickets contributed by India team

git branch -a | grep in_ 

Selecting base branch

Unless really required, the base branch should be master.
If some work is common to multiple tickets, a common branch should be created, rather then
duplicating code in multiple branches.
If the base branch is NOT Master, than branch should be named as 'in_t1234_basebranch'
Git does not provide a way to find the base branch later, so naming convention is important.

Oct 6, 2013

MOOC vs Crowd sourced education

MOOCs seem to be changing the way world learns. The success of Khan Academy perhaps helped coursera and udemy clinch precious VC money. Money and laurels helped them catch top notched 'educators' to deliver on line courses, and the whole world is learning from top faculty from top institutions. Perfect .. but what can be better !

This post is about some ideas, on how to port the open source software learning to creating open sourced content for courses. Essentially the argument here is, that  in addition to the facebook / yahoo / google / microsoft / apple's of the education , we also need github for the education. In fact a well done github for education can deplete the hill top education sites. Rather than beating the existing platforms, why not define the new platform.

What to we want to achieve from the platform ? In one word, it'll be 'crowd sourced'.
Imagine a site, where any one can create a content on any topic using very simple tools. This course gets translated to several languages in written and spoken, and also to braille.  Anybody in the world can send 'pull request' to the author of course, and just after a simple update, the new content is available to the rest of world instantly.  Taking the open source software legacy a little forward, some people can designate themselves as the 'packagers', who can define the syllabus, and packages the individual contents into a proper course.

This, has more potential, than any of today's hill-top educational sites.

To enumerate, what is needed is :

  1. machine  / crowd sourced translations to different languages
  2. machine / crowd sourced speaking out of courses in various languages
  3. discussions around each course, leading to it's crowd sourced improvement
  4. submitting a change to content should be very easy.
  5. All media : text, video, audio
  6. Self paced learning. Skip any part if you can clear the quiz
And do it all in a way that can scale up to thousands of courses ( yes .. courses !! )

Curious ? .. stay tuned ...




A New kind of browser

What would you want in a browser ?

There are already very good browser cores ( Gecko, Webkit ), and some very good packaging around them ( Firefox, Chrome and numerous others ). But are they, where we want them to be ?

Although browsers are helping a lot in protecting gullible users, it is still not enough. Does every internet users has a browser which is smarter and more evil than the bad forces of the internet. This post is about the features list of a vaporware browser , cozen. I'm hoping to make cozen alive some day.

So what are cozen's principles ? Only one .. security of data, above anything else. While looking innocent and obvious, this has some interesting repercussions.
  • Information entered or generated by user can only go to the designated site.
  • redone java script core to attach 'destination(s)' to each string
  • Two sites can't talk to each other on User's machine
  • Only HTML5. 
  • No native code plugins, ever, only javascript plugins.
  • Browser can't send a byte, that it can't show to user.
  • Cookie jars for each site or group of sites
  • Every data stored on disk is encrypted
  • Multiple passwords for varying sensitivity of data.
Well , waiting for that thing called free time to make cozen a reality...