12:05 我的公益脉络 » 刘润

捐献时间”(今天的慈善1+1,以及仁网)到现在三年多来,很多朋友、媒体、公益人士都在问:你是怎么想到这个模式的?遇到了什么困难?商业理念如何融入公益?你在赚钱吗?如果不赚钱,你为什么要做?你是党员或者基督徒吗?如何平衡效率和效果?你的团队怎么分工管理的?如何合作?如何管理冲突?你怎么看今天的公益?今天的公益真的如你所说,很象80年代的产业经济吗?那下面的趋势是什么?……

问题和兴趣点很多。

虽然这些问题大部分都在采访中回答了(部分留存在这里),但是我一直想系统的整理一下这些思路,围绕着“捐献时间”,理出一条我的“公益脉络”,沉淀一些或许对别人也有用的东西。

机会终于来了,我意外的得到了我的导师凌鸿教授的支持,同意我用这些所想,完成我的MBA论文。他的悉心指导,以及很多公益人士和商业人士的帮助,这些点滴零碎的想法终于慢慢的汇集、沉淀、成型。

由于时间以及自己能力、领悟力所限,这区区三万多字的论文当然还有很多的不足,甚至浅薄,但它是实践的总结,只希望能给今天从事公益、或者即将从事公益的人士提供某一个角度的观点,引起一点思考。

2008年是多灾多难的一年,希望在所有国民、政府、企业、公益组织的共同努力下,我们终能战胜一切困难!

下载地址:http://blog.run2me.com/files/runliu/paper.pdf

 

目录:
=====

摘  要    1
Abstract    2
1 引言    3
2 公益事业面临问题的研究    5
    2.1 什么叫公益组织    5
    2.2 公益精神的解析    5
        2.2.1 参加公益活动的动机    5
        2.2.2 慈善家精神    6
        2.2.3 志愿者精神    6
    2.3 公益力量构成分析    6
        2.3.1 公益组织的三种形式    7
        2.3.2 00年代公益和80年代经济的对比    7
        2.3.3 草根公益组织越来越重要    8
    2.4 公益事业的问题分析    9
        2.4.1 问题一:不透明    9
        2.4.2 问题二:不专业    9
    2.5 用电子善务解决公益的问题    11
3 电子善务的理论模型    12
    3.1 理论基础:基于网络C2C的公益要素市场    12
        3.1.1 公益要素市场    12
        3.1.2 网络C2C    15
    3.2 电子善务的C-R-C模型    17
        3.2.1 电子善务平台基本模型    17
        3.2.2 电子善务模型的核心要素    18
        3.2.3 典型的场景    20
        3.2.4 基于电子善务的“捐献时间”流程    22
        3.2.5 其他需要考虑的问题    23
4 电子善务的实践:“捐献时间”网站设计    27
    4.1 软硬技术选择    27
    4.2 网站功能设计    28
        4.2.1 总体功能逻辑设计    28
        4.2.2 主要业务流程设计    29
    4.3 数据结构设计    34
        4.3.1 数据对象简介    34
        4.3.2 表结构简介    37
    4.4 技术要点分析    38
        4.4.1 以邮件为基础    38
        4.4.2 新闻信    39
        4.4.3 实时数据更新    43
        4.4.4 自动匹配    45
        4.4.5 积分系统,建立信用    46
        4.4.6 Web 2.0的技术    47
        4.4.7 访问数据分析    50
5 电子善务实践的经验总结    52
    5.1 “捐献时间”网站实施成果    52
        5.1.1 一年创造218万元的社会价值    52
        5.1.2 组织过的活动列表(部分)    52
        5.1.3 通过电子善务匹配成功的志愿者活动案例    55
    5.2 推广电子善务值得借鉴的经验教训    59
        5.2.1 信息化技术可以帮助公益事业    59
        5.2.2 政府、媒体、企业是三把双刃剑    60
        5.2.3 经济规律:以需求(活动)拉动供给(捐赠)    62
6 “捐献时间”的下一步    64
    6.1 第一步:捐献时间,上海    65
    6.2 第二步:捐献时间,全国    65
    6.3 第三步:捐献金钱,香港    66
    6.4 第四步:捐献金钱,全国    67
7 注 释    68
8 参考书目    69
9 后记    70

08:48 MySQL 5.1 is to reach GA state - all to arms ! » MySQL Performance Blog

MySQL 5.1 was in RC stage for around 10 months now finally planned to be released as GA soon. As Monty Says MySQL 5.1.26 will be renamed as GA if no serious bugs are discovered.

Lets help MySQL to ensure GA release will be indeed GA quality and support Monty in his call to ensure this RC candidate works well for you.

If you know about any bugs in MySQL 5.1 or MySQL 5.0 (which are still unfixed in MySQL 5.1) make sure to report them on bugs.mysql.com. If there are some bugs already reported but still not fixed as of MySQL 5.1.26 make sure to post a comment to let MySQL know the bug is affecting you as well. The scream factor is important for bug fix prioritization so if you can make a story of your suffering because of the bug to slashdot you should be quite good.

If you’re the customer - make sure you put that note in your bug report. Bug reports from customers should be treated more seriously so make sure you use this advantage. And if you’re not a customer I guess one of your friends is so you can ask them to vote for a bug for you.

It also helps to be descriptive to explain why exactly this bug is important. Many MySQL developers are isolated to the customer so they may not quite understand how often bug circumstances happen and how bad are consequences.

It is surely helps to have repeatable bug reports but make sure to report bug even if you do not have one. If significant number of people are reporting similar issue it shows some problem exists, even if they can’t exactly pinpoint it. It helps MySQL with bug hunting and what is even more important it helps other users which know they are not alone and can find a workaround assuming fix does not exist.

In general I’m quite happy to see MySQL 5.1 is reaching GA stage and I think it is already better than Quality Disaster MySQL 5.0 initial release have been. Though I still think it is not quite where yet when it comes to Quality. Error rate with 5.1 we’ve seen among the customers during last few months was higher than with 5.0, also Scalability of MySQL 5.1 is often subpar compared to MySQL 5.0 possibly due to this bug which is not fixed up to now (not in 5.1.26 at least)


Entry posted by peter | No comment

Add to: delicious | digg | reddit | netscape | Google Bookmarks


^==Back Home: www.chedong.com

^==Back Digest Home: www.chedong.com/digest/

<== 2008-07-19
  七月 2008  
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      
==> 2008-07-21