Origins of AKA

Source: Internet
Author: User

Origins of AKA

Origins of AKAXiaobo (statement of the 11th inaugural meeting)

In May April this year, when I published several articles at Tsinghua, I did not think about what it actually meant for me.

At that time, I was working on the subject of network teaching and had a thought-Good idea. I called it eForum. The most basic idea of eForum is to combine WWW, BBS, FTP, Email, News Group, and other network forms into a complete system, I have always felt that the existing network teaching methods are insufficient.

I am very proud of this idea. However, at that time, the lab instructors did not pay much attention to this, and I also knew that such a system could not be implemented by myself and the strength of our lab alone.

Early on, I began to pay attention to "Software Engineering edition. I know that HansB and others once mentioned above that they want to conduct collaborative development through the network. Although I didn't have the following content, I know that many people are enthusiastic. So I want to give it a try.

I first built a website on my machine, explained my ideas, and made several articles related to software engineering, I hope to share my experience with others in this area. Then I ran to the software engineering edition and wrote several articles in one breath. The general idea is: I have a good idea. Let's go to my site and see how to conduct collaborative network development, and so on.

I name the development team AKA in English. Agka is the wild goose in the Travel Notes.

In the next few days, some people have joined the collaborative development.

So we met for the first time in a chat room in shuimu Tsinghua. In addition to introducing yourself, this discussion has no substantive results. Therefore, in the subsequent meeting minutes, I drew a bitter melon face. :(

Over the next week, we fell into silence. I feel a little discouraged. On the one hand, it is because of lack of organizational experience; on the other hand, it is also because of opposition from other people in the laboratory that I doubt the feasibility of collaborative development through the network.

The first attempt of this network collaboration is facing the danger of a collapse.

At this time, waterbird and others posted several articles on the software engineering edition to express their opinions and questions.

I think of it as a question to me and feel a bit embarrassed. I think I should assume my own responsibilities and take actions!

As a result, I raised questions that have been lingering for some time and asked everyone to answer them. It includes some questions about the organization method of AKA and her future development.

Many people expressed their views on this and also produced AKA's initial members.

We met again in the chatting room of shuimu Tsinghua and decided to meet each other immediately in front of the Tsinghua Auditorium on Sunday. Of course, today's Friday meeting and the gathering in front of the Sunday auditorium have become a convention.

We have made great achievements in our first meeting. In that discussion, we basically determined the development tone of AKA and some things that AKA had to do.

We also realized that there is still much work to be done to implement collaborative development on the network. Moreover, the eForum project is too huge for us. So we decided to put it first. In this way, the online collaboration development plan is aborted, but AKA is born.

Afterwards, we rebuilt the site as planned, set up several groups, and waterbird drafted the regulations.

In the middle, some people still join AKA, including iasc, who is a fellow of HansB University.

However, at the end of the term, everyone had to start busy with their own affairs. Wuqiong, doc, bornworm, and I are busy writing papers and graduation tasks. HiHint is temporarily out of AKA because the lab is too busy; HansB and sunray are far away in Changsha and Nanjing, respectively, they are also busy with their respective tasks.

For weeks, I started to wait in front of the auditorium at five o'clock P.M., but it was always waterbird and bornworm. Once, bornworm asked
Waterbird: How long does AKA last?

Yes, at that time, I often asked myself how long we could last, and how far should I go on this road? I also often hope that one day I could hand over this burden to another person.

As I said at the very beginning, when I published several articles at Tsinghua, I did not think about what it actually meant for me.

My ideal is humanistic, and I plan to give up on computer development for a while. However, when AKA came, it was like a baby who came to this world unexpectedly.

I gradually realized that this was not my personal task. AKA embodies the hopes and ideals of many people, as waterbird said: Aka is a signal and the starting gun of the next millennium. I think I accidentally pulled the trigger.

I know that I can't back up. It's shameful. Although it is often difficult for me to do such a thing without any organizational experience.

Goner once told me: maybe one day, everyone will leave AKA. At that time, you must stick to it. Persistence is victory. I don't know if he said that everyone was talking about the person who had dinner together or all of them. I felt a little sad and thought: if AKA is destined to be a failed attempt, then, I will be the last person to fall down.

Goner's words have always inspired me. I also understand what he meant: leaving is only temporary. Graduation, going abroad, and working cannot block our ideals. Yes, persistence is victory.

In March, we plan to keep a low profile during the summer vacation, avoid too much attention, and avoid new members from joining us. To be down-to-earth, first build the site and organizational structure, and then start to take some formal actions after the school starts.

However, this is not the case.

First, iasc discovered Tachi. In Banly's "torrent", Tachi wrote an article called "century Mania", describing his idea of developing China's information industry, we propose to create an organization called "China Information Technology Forum.

Therefore, we contacted Tachi and both parties had a sense of mutual sorrow, so we decided to merge. The merged organization is officially named "China Information Technology Forum", and AKA is its nickname.

After that, I started to use Domino to rebuild the site. Due to lack of manpower, I published an article on recruiting volunteers to build a site with Domino at Tsinghua. At the same time, I published an article titled "The dream of a free programmer.

These actions broke our original plan and attracted many new members. This forces us to speed up.

In early August, iasc came to Beijing from Wuhan. So we took this opportunity to have a party. This gathering includes iasc, goner, rivercool, waterbird, BlueOcean, boya, mikehe, and myself. For details about this gathering, I wrote a report for the gathering, which can be found in the current Message version.

Since then, we have resumed the Friday meeting and the gala on Sunday. Although bornworm has already gone to Shenzhen, wuqiong is too busy to work. doc has no conditions to access the Internet on Yuquan Road. Now there are several new "old faces ": goner, rivercool, mikehe ......

AKA is finally on track.

Today, after a long journey, AKA can finally take off. However, I feel that even now, we still need to be cautious about moving forward. I have always been worried that one day, due to our continuous and excessive expansion, AKA will eventually dissipate.

However, in any case, I think we are the people who are at the forefront of this era. If history really gives us such a role and requires us to develop ahead, let us bravely assume our mission!

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.